Re: [Django] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
-+-
 Reporter:  mtredinnick  |Owner:  Xof
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 Django now support persistent connections, which alleviate the overhead of
 version checking. And Malcolm will never do what he had in mind.

 Considering that there isn't a concrete proposal and that there hasn't
 been much activity in three years, I'm going to close this ticket.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.066cead62543310ebf68b358db4b388b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
-+-
   Reporter: |Owner:  Xof
  mtredinnick|   Status:  assigned
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by ramiro):

 In [16439]:
 {{{
 #!CommitTicketReference repository="" revision="16439"
 Fixed #11065, #11285 -- Streamlined PostgreSQL version detection, fixing
 incompatibility with multi-db. Thanks findepi for the report.

 Changed our internal representation of the PostgreSQL version from tuples
 to
 integers as used by libpq and psycopg2. This simplifies version comparison
 operations.

 Also, using the associated libpq/psycopg2 API allows to remove the need
 for
 manually issuing in-band ``SELECT version()`` SQL queries to obtain the
 server
 version (or at least reduce its number if version of psycopg2 in use is
 older
 than 2.0.12). Refs #10509.
 }}}

-- 
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] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
-+-
   Reporter: |Owner:  Xof
  mtredinnick|   Status:  assigned
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by SmileyChris):

 * type:   => Bug
 * severity:   => Normal


-- 
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] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
---+
  Reporter:  mtredinnick   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Richard Davies ):

 * cc: richard.dav...@elastichosts.com (added)

-- 
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] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
---+
  Reporter:  mtredinnick   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 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
-~--~~~~--~~--~--~---

[Django] #10509: Better handling of database version-specific feature initialisation

[Django]

#10509: Better handling of database version-specific feature initialisation
--+-
 Reporter:  mtredinnick   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Right now, we have problems such as those mentioned in #10467 (comment 4).
 If a part of Django wants to use a particular feature that depends on the
 database version, it needs to first have talked to the database. This
 breaks in some edge-cases.

 Some alternative possibilities are

  1. understanding deferred-features, but that looks hard. For example,
 it's difficult to imagine how "return ID from insert" can work in that
 fashion without being really ugly code.
  2. requiring the settings file to include the version information so we
 don't have to make the wasteful `SELECT version();` (or equivalent) call
 for every database connection. It's essentially unchanging information.

 Anyway, that's a discussion for later (I'll start a thread on django-dev
 at some point). Opening the ticket to remind me to look at this.

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