Foreign key not created for class "Project"

[Darren <spaceship@…>]

Foreign keys look like they're not being created correctly if the class is named "Project".

Here's sample code:

from django.db import models

class Client(models.Model):
    name = models.CharField(maxlength=200)
    shortname = models.CharField('short name', maxlength=5)
    datecreated = models.DateTimeField('date created')

class Project(models.Model):
    client = models.ForeignKey(Client)
    name = models.CharField(maxlength=200)
    datecreated = models.DateTimeField('date created')

Results in this:

C:\temp\django\temp\timeserver>manage.py sql timesheet
BEGIN;
CREATE TABLE "timesheet_project" (
    "id" integer NOT NULL PRIMARY KEY,
    "client_id" integer NOT NULL,
    "name" varchar(200) NOT NULL,
    "datecreated" datetime NOT NULL
);
CREATE TABLE "timesheet_client" (
    "id" integer NOT NULL PRIMARY KEY,
    "name" varchar(200) NOT NULL,
    "shortname" varchar(5) NOT NULL,
    "datecreated" datetime NOT NULL
);
COMMIT;

Note lack of foreign key relationship on timesheet_project.client_id

However (note class Project renamed to Projecta) works:

from django.db import models

class Client(models.Model):
    name = models.CharField(maxlength=200)
    shortname = models.CharField('short name', maxlength=5)
    datecreated = models.DateTimeField('date created')

class Projecta(models.Model):
    client = models.ForeignKey(Client)
    name = models.CharField(maxlength=200)
    datecreated = models.DateTimeField('date created')

Results in this:

C:\temp\django\temp\timeserver>manage.py sql timesheet

BEGIN;
CREATE TABLE "timesheet_client" (
    "id" integer NOT NULL PRIMARY KEY,
    "name" varchar(200) NOT NULL,
    "shortname" varchar(5) NOT NULL,
    "datecreated" datetime NOT NULL
);
CREATE TABLE "timesheet_projecta" (
    "id" integer NOT NULL PRIMARY KEY,
    "client_id" integer NOT NULL REFERENCES "timesheet_client" ("id"),
    "name" varchar(200) NOT NULL,
    "datecreated" datetime NOT NULL
);
COMMIT;

Environment:

Python 2.5.1, Windows Vista, Django 0.96, sqlite3 database

[James Bennett]

This is arguably the correct thing to do; SQLite parses and accepts declarations of FOREIGN KEY constraints, but does not enforce them or base any functionality on them.

[James Bennett]

Wait, no, missed the second bit. That is a bit weird.

[Peter Baumgartner]

Problem does not appear to be SQLite dependent. Confirmed on both MySQL 4.1.22 and SQLite 3.3.16

[Philippe Raoult]

confirmed in SVN. It appears to be related to the order in which the models are outputed in SQL. If Project model is defined first, it won't have the FK. If it is defined after it will. The order seems to be related to the name but I don't know how exactly (probably a dict ordering?).

[Philippe Raoult]

a similar issue is mentionned in #4930 (this time with models in different apps).

[Philippe Raoult]

dup of #4193 which is more documented.