Hi all,
On Saturday 14 February 2015 22:53:13 Marc Tamlyn wrote:
>
> Django 1.8 will necessarily be the first version with a true minimum
> requirement on psycopg2 version. Historically we have never documented a
> required version.
>
FWIW, we have long had minimum requirements for other backen
Hi all,
Related ticket - https://code.djangoproject.com/ticket/24335
Django 1.8 will necessarily be the first version with a true minimum
requirement on psycopg2 version. Historically we have never documented a
required version.
- The new UUIDField requires at least 2.0.9
- Some code which is cu
This issue is that the foreign key field (i.e. the foo_id field) does not
have its db_converters called, if they are defined in the backend rather
than in the field itself.
I've added a pull request (https://github.com/django/django/pull/4134) with
a possible approach to the problem. We may be abl
Long term, eventually we want the FK to use a real models.UUIDField under
the hood, right?
On Sat, Feb 14, 2015 at 1:17 PM, Shai Berger wrote:
> Hi all,
>
> This comes from trying to fix #24343[1] -- a problem where a UUIDField is
> used
> as a PK (legitimate and common practice), and we wish to
Hi all,
This comes from trying to fix #24343[1] -- a problem where a UUIDField is used
as a PK (legitimate and common practice), and we wish to test a FK to that
model. The problem is that, on database backends which do not support native
UUIDFields (that is, all but postgres), the underlying f
