#11065: Improve version comparison functions, esp for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: russellm | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Component: Database layer
Milestone: | (models, ORM)
Version: 1.0 | Severity: Normal
Resolution: fixed | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by ramiro):
* status: new => closed
* resolution: => fixed
Comment:
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: <https://code.djangoproject.com/ticket/11065#comment:3>
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 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.
