Re: [Django] #18130: postgres_psycopg2 adapter should not use hard coded isolation levels

[Django]

#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-+-
 Reporter:  limscoder|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgres |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"e0449316ebacaa550e9c529f8c9cb9a9b44e3765"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e0449316ebacaa550e9c529f8c9cb9a9b44e3765"
 Fixed #18130 -- Made the isolation level configurable on PostgreSQL.

 Thanks limscoder for the report and niwi for the draft patch.
 }}}

-- 
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] #18130: postgres_psycopg2 adapter should not use hard coded isolation levels

[Django]

#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-+-
 Reporter:  limscoder|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgres |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by niwi):

 I think, does not need any kind of magic by django, as you say: "This
 isolation level is for people who know what they're doing."

 I now update the patch with some checks for isolation_level value and
 documentation notes with warning.

-- 
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] #18130: postgres_psycopg2 adapter should not use hard coded isolation levels

[Django]

#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-+-
 Reporter:  limscoder|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgres |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Yes, we could provide a way to switch to "serializable" for people with
 high concurrency and integrity requirements.

 IIRC, under the "serializable" isolation level, the application should be
 prepared to handle transaction failures (and possibly retry) on every
 database query. I'm not sure we can handle this automatically in Django
 without introducing magic. It deserves a fat warning in the documentation.
 This isolation level is for people who know what they're doing :)

 NB: there is some material on this topic in #3460.

-- 
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] #18130: postgres_psycopg2 adapter should not use hard coded isolation levels

[Django]

#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-+-
 Reporter:  limscoder|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  postgres |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by niwi):

 * cc: niwi@… (added)
 * has_patch:  0 => 1


Comment:

 Here the patch to allow to define the default isolation_level parameter on
 database configuracion dict:
 https://github.com/niwibe/django/compare/issue_18130

 I ran the tests (not all tests) and I have not seen any fail that might be
 related.

-- 
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] #18130: postgres_psycopg2 adapter should not use hard coded isolation levels (was: postgres_psycopg2 adapter uses hard coded isolation levels)

[Django]

#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-+-
 Reporter:  limscoder|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  postgres |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by limscoder):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0


-- 
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.