[Django] #25175: Create an alias for the postgresql_psycopg2 database backend
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: 1.8
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The name is too complicated and personally, I can never get it right the
first time.
In the discussion on the mailing list [1], it was suggested to actually
create two aliases: `postgresql` and `postgres`. I have no preference one
way or the other.
[1] https://groups.google.com/forum/#!topic/django-developers/o7qFItlHILc
--
Ticket URL: <https://code.djangoproject.com/ticket/25175>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Given that Postgres was
[https://wiki.postgresql.org/wiki/FAQ#What_is_PostgreSQL.3F_How_is_it_pronounced.3F_What_is_Postgres.3F
renamed] to PostgreSQL a few years ago, I think that `postgresql` is a
better name.
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner: nobody
Type: | Status: new
Cleanup/optimization |
(models, ORM) |
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* stage: Unreviewed => Accepted
Comment:
As all other database names are named according to their database, I agree
with Aymeric that postgresql is a better name.
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner:
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => assigned
* owner: nobody => caioariede
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:3>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner:
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by caioariede):
Pull request: https://github.com/django/django/pull/5107
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner:
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
Comment:
Please don't forget to check "Has patch" so the ticket appears in the
review queue.
As I mentioned on the pull request, I think we could leave the alias
without an immediate deprecation. Mainly because I don't want to have to
vary the settings on Jenkins (which are used for multiple versions of
Django) based on the Django version. I guess it would save third-party
apps some hassle too.
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner:
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ec9004728ee136e3b7e2b7cd2610203e16b6ce9b" ec900472]:
{{{
#!CommitTicketReference repository=""
revision="ec9004728ee136e3b7e2b7cd2610203e16b6ce9b"
Fixed #25175 -- Renamed the postgresql_psycopg2 database backend to
postgresql.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:6>
Django
-------------------------------------+-------------------------------------
Reporter: bmispelon | Owner:
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"bcb4fe0012f8f869348ea83f5a35706f4545c44a" bcb4fe00]:
{{{
#!CommitTicketReference repository=""
revision="bcb4fe0012f8f869348ea83f5a35706f4545c44a"
Refs #25175 -- Added backwards compatibility for importing
postgresql_psycopg2 backend.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:7>
Django
-------------------------------------+-------------------------------------
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"3f0c4fe18fe9850bb2f56be138012add4b54873d" 3f0c4fe]:
{{{
#!CommitTicketReference repository=""
revision="3f0c4fe18fe9850bb2f56be138012add4b54873d"
Refs #25175 -- Deprecated db.backends.postgresql_psycopg2 module.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:8>
Django
-------------------------------------+-------------------------------------
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"944469939b9eb93fda0924f78faba5c0ffae2dff" 94446993]:
{{{
#!CommitTicketReference repository=""
revision="944469939b9eb93fda0924f78faba5c0ffae2dff"
Refs #25175 -- Removed db.backends.postgresql_psycopg2 per deprecation
timeline.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:9>
Django
-------------------------------------+-------------------------------------
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"ddb293685235fd09e932805771ae97f72e817181" ddb29368]:
{{{
#!CommitTicketReference repository=""
revision="ddb293685235fd09e932805771ae97f72e817181"
Refs #25175 -- Renamed test file referencing the old postgresql_psycopg2
engine.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:10>
Django
-------------------------------------+-------------------------------------
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"6cdc7ae23f5aa7866bdcf6bb536d600e9706204b" 6cdc7ae]:
{{{
#!CommitTicketReference repository=""
revision="6cdc7ae23f5aa7866bdcf6bb536d600e9706204b"
[2.2.x] Refs #25175 -- Renamed test file referencing the old
postgresql_psycopg2 engine.
Backport of ddb293685235fd09e932805771ae97f72e817181 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:11>
Django
-------------------------------------+-------------------------------------
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"5bcba16c0120d4a1bb661f0a495dc47f5ed5465d" 5bcba16c]:
{{{
#!CommitTicketReference repository=""
revision="5bcba16c0120d4a1bb661f0a495dc47f5ed5465d"
Refs #25175 -- Removed postgresql_psycopg2 in
django.db.utils.load_backend().
Follow up to 944469939b9eb93fda0924f78faba5c0ffae2dff.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25175#comment:12>