Wouldn't the second / "foolproof" way described here be a good choice
for the default Pyramid implementation? Just as a safety measure.

http://docs.sqlalchemy.org/en/latest/core/pooling.html#using-connection-pools-with-multiprocessing

On 2 April 2018 at 18:32, Jonathan Vanasco <[email protected]> wrote:
>
>
> On Monday, April 2, 2018 at 12:07:14 PM UTC-4, Bert JW Regeer wrote:
>>
>>
>> This is only required if you are not using pyramid_tm. If you are using
>> pyramid_tm which is what the sqlalchemy cookie cutter does, you do NOT need
>> to add this.
>
>
> Thanks, Bert.  I stand corrected.  pyarmid_tm has a finish() that eventually
> calls a session.close() in Zope.SqlAlchemy.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "pylons-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pylons-discuss/_MJflNUcjdg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/e1f81475-8b31-44ca-b0cf-af3448a3b131%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CAKw-smAQ5QWad0eBA60MTDNS9EBxCrxV%3D4wDQT%3DxvnERP%2BUOhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to