On Nov 12, 2012, at 9:37 PM, Michael Bayer wrote:
>
> On Nov 12, 2012, at 5:33 PM, Torsten Landschoff wrote:
>
>>
>> BTW, I found one offender that breaks running database upgrades with my
>> locking schemes:
>>
>> from sqlalchemy import *
>> from sqlalchemy.pool import *
>>
>> engine = crea
On Nov 12, 2012, at 5:33 PM, Torsten Landschoff wrote:
>
> BTW, I found one offender that breaks running database upgrades with my
> locking schemes:
>
> from sqlalchemy import *
> from sqlalchemy.pool import *
>
> engine = create_engine("sqlite:home/torsten/some.db",
> poolclass=Assertion
Hi Michael,
On 11/09/2012 11:36 PM, Michael Bayer wrote:
> On Nov 8, 2012, at 5:01 PM, Torsten Landschoff wrote:
>> My first tests with the SQLAlchemy core where promising, but when using
>> the ORM I get a bunch of deadlocks where it seems like the session opens
>> two connections A and B where A
On Nov 8, 2012, at 5:01 PM, Torsten Landschoff wrote:
>
> My first tests with the SQLAlchemy core where promising, but when using
> the ORM I get a bunch of deadlocks where it seems like the session opens
> two connections A and B where A locks B out.
The Session never does this, assuming just
