catalyst

I'm studying to take the data bricks to spark certification exam, and their practice exam ( please see > https://databricks-prod-cloudfront.cloud.databricks.com/public/793177bc53e528530b06c78a4fa0e086/0/6221173/100020/latest.html ) requires us to accept this statement as true fact: "Explicit caching can decrease application performance by interfering with the Catalyst optimizer's ability to optimize some queries" I got this question wrong even though I have read up a lot on the catalyst and have a pretty good grasp of the details. So I wanted to shore up my knowledge of this topic and go to

I have a series of Moose objects that I'm looking to feed to JSON::XS by way of Catalyst::View::JSON . JSON::XS is unable to encode blessed data-structures. I know that there is MooseX::Storage::Format::JSON which can -- kinda -- do what I want; but, it seems pretty overly heavy. What I'm looking for is essentially the same information that XXX.pm provides. I just want the raw-data structures recursively unblessed so JSON::XS (the driver for JSON::Any that C:V:JSON uses internally) can display it. What is the best way go about using Catalyst::View::JSON and JSON::XS with Moose objects? It

I've tried to use parse_on_demand as shown in: http://search.cpan.org/~flora/Catalyst-Runtime-5.80007/lib/Catalyst.pm#ON-DEMAND_PARSER However, I can't seem to stop the upload. I'm testing this simply by creating an action that dies immediately, however the browser seems to upload the very large file I've selected before it ever reaches my action: sub upload :Local { my ($self, $c) = @_; die; # What I'd like to do is this: # if ($c->req->header('Content-Length') > $some_limit) { # die "Upload too large"; # } # ... check filename extension and mime-type... } Is this the right way to approach

I'm struggling with fairly fundamental DBIx-Class prefetch usage. I want to limit the columns that are returned from joined tables when prefetch is used. This: my $rs = $schema->resultset('CD')->search( {}, # No searching restrictions through WHERE clause { prefetch => [qw/ artist /], columns => [qw/ title artist.name /], } ); Generates this SQL: SELECT cd.title, artist.* FROM cd JOIN artist ON cd.artist = artist.id But I don't want to haul down all of the artist columns, just the cd.title and artist.name columns (in this example, my real use case is more complex). The columns feature seems to

I just used catalyst for my first large project and I was left wondering if I used catalyst in the way it was meant to be used. I have Root.pm and inside of that file I put multiple url handlers. Is it a best practice to have one controller per url or should a grouping be considered? One of the beauties of Catalyst is its flexibility. You can do this however it best suits your application. If you only have a handful of URLs you support, then there's nothing intrinsically wrong with putting them all in Root.pm. Particularly if there's no depth, ie localhost:3000/foo and localhost:3000/bar