> The "Django Way" is essentially to work on the assumption that
> everything is as Django left it (or in a state that is compatible with
> Django's requirements). We provide handles to make integrating with
> legacy databases a little easier (such as allowing specification of
> db_column names, e
On 12/1/07, mtrier <[EMAIL PROTECTED]> wrote:
>
> With the current design the table and foreign key information is
> pulled together from the model information itself. The problem with
> that is that if someone manually changes the name of an foreign key
> constraint or removes the constraint ent
I'm was confirming ticket #2493 (Error resetting app with self-
referencing ForeignKey) this evening and as I began to poke into it it
appears that the fix is what mtredinnick recommended, to use
introspection to get the foreign key relation name when constructing
the alter table drop statement fo
