Django and Postgres

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Django and Postgres
Date: 2015-04-06 15:58:38
Message-ID: 5522AD2E.4030905@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Django 1.8 was just released so I was reading the Release Notes which
led me to this:

https://docs.djangoproject.com/en/1.8/ref/contrib/postgres/
"
Note

Django is, and will continue to be, a database-agnostic web framework.
We would encourage those writing reusable applications for the Django
community to write database-agnostic code where practical. However, we
recognize that real world projects written using Django need not be
database-agnostic. In fact, once a project reaches a given size changing
the underlying data store is already a significant challenge and is
likely to require changing the code base in some ways to handle
differences between the data stores.

Django provides support for a number of data types which will only work
with PostgreSQL. There is no fundamental reason why (for example) a
contrib.mysql module does not exist, except that PostgreSQL has the
richest feature set of the supported databases so its users have the
most to gain.
"

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2015-04-06 17:13:44 Re: Django and Postgres
Previous Message Joshua D. Drake 2015-04-06 15:24:45 Re: OSCON 2015 Booth/BoF