On 2/28/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> Actually, PySQLite 2.x does an implicit commit after any DDL
> statement. I don't think this is enforced at the SQLite level, but
> supposedly the PySQLite author had reasons to do this in the bindings.
Do you know what the reasons were, or where we should look for them?
The spec sez no implicit commits:
"
Note that
if the database supports an auto-commit feature, this must
be initially off. An interface method may be provided to
turn it back on.
"
Given that there's almost no other discussion of transaction behavior,
I think this should have some weight. Since I'm poking at SQL Server
support (which also does auto-commit), I'd like to know what the issue
was before stepping in it.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
