Re: [Catalyst] Returning error codes to the user.

2010-05-02 Thread Bill Moseley
On Sat, May 1, 2010 at 6:17 PM, Tomas Doran bobtf...@bobtfish.net wrote: So, what would you recommend? Have a separate /user/$id/debug method that does a separate step-by-step of the business logic? Scrap all that really handy chaining of resultsets that works so well with Catalyst's

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-05-02 Thread Matt S Trout
On Fri, Apr 30, 2010 at 02:38:50PM -0700, Steve Kleiman wrote: Here goes...hopefully a simple test case for the RunAfterRequest oddness. The code below with the forward INSIDE 'run_after_request' subroutine throws the error: [error] Caught exception in engine Modification of non-creatable

Re: [Catalyst] Returning error codes to the user.

2010-05-02 Thread Matt S Trout
On Fri, Apr 30, 2010 at 04:18:46PM -0700, Bill Moseley wrote: I have a CRUD interface to an application. This is used for both the Web and directly as an API. The model uses DBIC which, as you know, allows chaining resultsets, which I use to add additional constraints to the result set.

Re: [Catalyst] Returning error codes to the user.

2010-05-02 Thread Bill Moseley
On Sun, May 2, 2010 at 12:53 PM, Matt S Trout m...@shadowcat.co.uk wrote: Am I correct in thinking that's built up in multiple -search calls? Somewhat, yes. ... if you keep all the intermediate resultsets around in the stash or wherever (or better still refactor to resultset methods and

Re: [Catalyst] RunAfterRequest/delayed Catalyst view

2010-05-02 Thread Steve Kleiman
Wow, Matt. That works like a charm. THANK YOU. No pointing and laughing from this corner. Except at myself for not setting up a proper email dispatching mechanism. One bridge at a time. Again, my thanks for tracking that down. Steve Kleiman st...@prodhub.com On May 2, 2010, at 12:49 PM,