#15506: Savepoint support for sqlite3 backend
-------------------------------------+-------------------------------------
     Reporter:  lamby                |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Database layer       |                  Version:  1.2
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  1                    |  Patch needs improvement:  1
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by niwi):

 * cc: niwi@… (added)


Comment:

 I could not find the official announcement, but according to the
 documentation of APSW:
 > Savepoints were introduced in SQLite 3.6.8
 (http://apidoc.apsw.googlecode.com/hg/pysqlite.html#what-apsw-does-better)

 I've done my own tests, comments in the code that clarify some things that
 I found and contrasting with official documentation of sqlite and
 pysqlite: https://gist.github.com/3061376

 This case is very similar to #14204, the difference is the minimum version
 of sqlite.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/15506#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to