On Wed, Dec 17, 2014 at 5:47 PM, Jan Henning Thorsen <jan.henn...@thorsen.pm > wrote: > > You should handle the error somehow. If you don't want to, then the best > strategy is simply to "die $err if $err;". That way, the error will > propagate correctly and result in a 500 page.
Of course, I can wrap all non-blocking requests through mojo::pg in eval and handle errors, but it is not common to do in asynchronous programming. Callback function should always be called at any non-blocking method. And I'm concerned that non-blocking methods can throw exceptions. -- Andrey Khozov -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To post to this group, send email to mojolicious@googlegroups.com. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
