On 18/07/11 11:25, James Henstridge wrote: > If all adapters that support transactions function like that, then I > think it would be sensible to require them to raise an error in that > case. If they don't raise an error, you know that someone somewhere > is going to write code like the following: > > with transaction: > # do stuff > with transaction: > # do more stuff > > ... and wonder why things break.
This can make sense for backends that support check points (subtransactions). PostgreSQL is an example (even if we don't yet support checkpoints in psycopg). federico -- Federico Di Gregorio federico.digrego...@dndg.it Studio Associato Di Nunzio e Di Gregorio http://dndg.it Quis custodiet ipsos custodes? -- Juvenal, Satires, VI, 347 _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
