On Feb 26, 6:13 pm, Ben Bangert <[email protected]> wrote:
> Since an exception goes past Beaker, it does not save the session. Generally > that is also not desired behavior since something bad happened. If you really > want to save the session, manually persist it to the backend with > session.persist() which will actually force it to save the data out, before > raising an exception. Great! Thanks! I actually do want to save the session, because i'm trying to design some integrated tests -- and its taking me forever to start from scratch each time. Incidentally -- does beaker now only 'persist' once per Pylons request ? I remember a while back that it would persist on each save , and i saw that someone had offered a patch to change that. i'm guessing that patch made its way into trunk ? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
