Context Navigation

← Previous Ticket
Next Ticket →

#25175 closed Cleanup/optimization (fixed)

Create an alias for the postgresql_psycopg2 database backend

Reported by:	Baptiste Mispelon	Owned by:	Caio Ariede
Component:	Database layer (models, ORM)	Version:	1.8
Severity:	Normal	Keywords:
Cc:		Triage Stage:	Accepted
Has patch:	yes	Needs documentation:	no
Needs tests:	no	Patch needs improvement:	yes
Easy pickings:	no	UI/UX:	no

Description ¶

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

Change History (12)

comment:1 by Aymeric Augustin, 10 years ago

Given that Postgres was renamed to PostgreSQL a few years ago, I think that postgresql is a better name.

comment:2 by Wim Feijen, 10 years ago

Triage Stage:	Unreviewed → Accepted

As all other database names are named according to their database, I agree with Aymeric that postgresql is a better name.

comment:3 by Caio Ariede, 10 years ago

Owner:	changed from nobody to Caio Ariede
Status:	new → assigned

comment:4 by Caio Ariede, 10 years ago

Pull request: https://github.com/django/django/pull/5107

comment:5 by Tim Graham, 10 years ago

Has patch:	set
Patch needs improvement:	set

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.