Message106689
@exarkun: yes, but since the module is already tracking that information, it seems silly to duplicate it in my code, especially since that duplication could include data-losing bugs.
@l0nwlf: its behaviour is in accord with the module documentation, which talks about the fact that issuing a create statement (for example) commits the current transaction. So in_transaction is an accurate representation of what sqlite3 is actually doing. |
|
Date |
User |
Action |
Args |
2010-05-28 20:23:47 | r.david.murray | set | recipients:
+ r.david.murray, ghaering, exarkun, l0nwlf |
2010-05-28 20:23:47 | r.david.murray | set | messageid: <1275078227.12.0.324137106226.issue8845@psf.upfronthosting.co.za> |
2010-05-28 20:23:45 | r.david.murray | link | issue8845 messages |
2010-05-28 20:23:45 | r.david.murray | create | |
|