Hi there,
I have seen some basic examples online showing that SQLAlchemy
supports twophase = True for some databases.
My question is I am needing to use this sort of functionality with 2
SQLite databases, does SQLAlchemy support SQLite two phase commits?
So here is some basic code
King Simon-NFHD78 wrote:
Jo wrote:
[SNIP]
and-
In [13]: aa=Anagrafica.get(111)
In [14]: aa.delete()
In [15]: aa.flush()
-
but in version 0.6 I can't find
Problems with flush() again...
I thougth I could avoid the use of flush() by nesting the mappers,
but...
I have two mappers:
mapper(CatalogazioneModulistica,
tbl['catalogazione_modulistica'],
column_prefix = 'catalogazione_modulistica_',
)
and:
mapper(GestioneDocFile,
Lynton Grice wrote:
Hi there,
I have seen some basic examples online showing that SQLAlchemy
supports twophase = True for some databases.
My question is I am needing to use this sort of functionality with 2
SQLite databases, does SQLAlchemy support SQLite two phase commits?
SQLite does not
Hi Michael,
Thanks for the feedback, much appreciated.
Seems I had to do some fancy foodwork using the Python SQLite3
library.and using the ATTACH DATABASEseems to work of for
what I need
Thanks
conn = sqlite3.connect('db_1.db')
c = conn.cursor()
result =
Hi, everybody!
Looks like mysql_python is getting some competition lately.
Not that there's a lot to complain about it, but having options never
heart anybody.
I'd be nice to get a grasp of what's the experience people had with
official connector and the our_sql (pure python sounds like not a