On Wednesday, April 6, 2016 at 8:14:02 PM UTC-4, Jeff Dairiki wrote:
>
>
> I'm not very familiar with the stock scaffold. I just went to look at it
> and was initially confused, since the scaffold in the master branch
> currently uses a reified request property to construct the SqlAlchemy
> s
On Wed, Apr 6, 2016 at 12:57 PM, Jonathan Vanasco
wrote:
> I edited my original post before hitting submit, and managed to clear out
> the important stuff. Ha.
>
> On Wednesday, April 6, 2016 at 2:42:38 PM UTC-4, Jeff Dairiki wrote:
>>
>> I use a reified request property to create the SqlAlchemy
I edited my original post before hitting submit, and managed to clear out
the important stuff. Ha.
On Wednesday, April 6, 2016 at 2:42:38 PM UTC-4, Jeff Dairiki wrote:
>
> I use a reified request property to create the SqlAlchemy session.
> The factory function adds an "add_finished_callback" t
I use a reified request property to create the SqlAlchemy session. The
factory function adds an "add_finished_callback" to close the session.
(Why don't you have access to the request?)
On Wed, Apr 6, 2016 at 11:30 AM, Jonathan Vanasco
wrote:
> A few routes I have need to explicitly commit the
A few routes I have need to explicitly commit the session, and require me
to use "long lasting sessions"
(https://pypi.python.org/pypi/zope.sqlalchemy#long-lasting-session-scopes)
Since this disables transaction's call to "close" on commit, what is the
best way to close the SqlAlchemy session?
