Re: [Django] #15506: Savepoint support for sqlite3 backend

[Django]

#15506: Savepoint support for sqlite3 backend
-+-
 Reporter:  lamby|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  duplicate
 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 claudep):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 This was already reported in #13742.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15506: Savepoint support for sqlite3 backend

[Django]

#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|
-+-

Comment (by niwi):

 I think you should go deprecating older versions of sqlite to equal what
 is being done with support for versions of python. And take advantage of
 the new things that are incorporated sqlite.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15506: Savepoint support for sqlite3 backend

[Django]

#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: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15506: Savepoint support for sqlite3 backend

[Django]

#15506: Savepoint support for sqlite3 backend
+---
   Reporter:  lamby | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---
Changes (by russellm):

  * needs_docs:  => 0
  * needs_better_patch:  => 1
  * needs_tests:  => 0
  * stage:  Unreviewed => Accepted


Comment:

 As with #15507 -- if SQLite supports a feature, we should to.

 Same comment goes for the patch -- are you sure the feature check is
 correct? Has this feature always been available? What are you basing your
 assertion about autocommit upon (I can't find any reference to this
 limitation from a quick scan of the SQLite docs on savepoints)

 See also #14204 -- support for FK constraints in SQLite.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15506: Savepoint support for sqlite3 backend

[Django]

#15506: Savepoint support for sqlite3 backend
--+-
 Reporter:  lamby |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Database layer (models, ORM)  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 We can enable savepoints on sqlite if the user has set
 `isolation_level=None` in their OPTIONS dict (or they have otherwise set
 the `isolation_level` to  `None`) on the
 `django.db.connections.connection` sqlite instance. The default is `''`
 (empty string).

 Patch attached.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.