When using syncdb
the following schema is created:
CREATE TABLE "MyApp_supervisor" (
"id" integer NOT NULL PRIMARY KEY,
"supervisor_id" integer NOT NULL REFERENCES "MyApp_employee" ("id"),
"section_id" integer NOT NULL REFERENCES "MyApp_section" ("id")
);
When using migrate
, it is changed to:
CREATE TABLE "MyApp_supervisor" (
"id" integer NOT NULL PRIMARY KEY,
"supervisor_id" integer NOT NULL,
"section_id" integer NOT NULL
);
Why does South do that? I haven't noticed a functional problem yet, but I'm weary of ignoring this...
Can someone shed some light on what is happening here?