Am 21.12.2013 16:27, schrieb Michael Bayer:
In the case of using Postgresql, the type
sqlalchemy.dialects.postgresql.INTERVAL takes over wherever you might
have used a sqlalchemy.Interval type.In this case, psycopg2 is
what’s doing whatever conversions are occurring here - if a result
row
On Dec 23, 2013, at 9:29 AM, Sibylle Koczian nulla.epist...@web.de wrote:
Am 21.12.2013 16:27, schrieb Michael Bayer:
In the case of using Postgresql, the type
sqlalchemy.dialects.postgresql.INTERVAL takes over wherever you might
have used a sqlalchemy.Interval type.In this case,
On Monday, 23 December 2013 06:38:41 UTC-8, Michael Bayer wrote:
On Dec 23, 2013, at 9:29 AM, Sibylle Koczian nulla.e...@web.dejavascript:
wrote:
Am 21.12.2013 16:27, schrieb Michael Bayer:
In the case of using Postgresql, the type
sqlalchemy.dialects.postgresql.INTERVAL takes
On Thursday, 12 December 2013 15:26:08 UTC-8, Thierry Florac wrote:
Hi,
I'm using two-phase transactions with ZODB, PostgreSQL and Oracle
databases connected with SQLAlchemy without problem.
I'm not using native zope.sqlalchemy package, but another package called
ztfy.alchemy that I've
On Thursday, 12 December 2013 16:30:59 UTC-8, Jeff Dairiki wrote:
Do you understand why the datamanager is finding the SessionTransaction
and using that directly? (At least I think that's what it's doing ---
I haven't sussed this out completely.) I'm referring to the line from