- Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
[snip]
> Have a poke around in django/core/management.py in the
> _get_sql_model_create() function and see if you can work out why we're
> getting this wrong.
>
> The fact that the generated SQL has a "...REFERENCES ..." clause on the
> problem
[snip]
> Looks like the problem is in _get_many_to_many_sql_for_model().
> Unfortunately, it doesn't check to see whether or not the table exists
> before generating a reference. Is there somewhere else where the
> models are ordered by dependency before creation?
Looking further, you're right
- Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Thu, 2006-08-10 at 05:55 -0400, John Szakmeister wrote:
> > Now that the magic has been removed, and Django released 0.95, I
> decided to start porting my applications over. I knew the merge of
> magic-removal was coming, so I never deploy
- Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
[snip]
> Have a poke around in django/core/management.py in the
> _get_sql_model_create() function and see if you can work out why we're
> getting this wrong.
>
> The fact that the generated SQL has a "...REFERENCES ..." clause on the
> problem
On Thu, 2006-08-10 at 05:55 -0400, John Szakmeister wrote:
> Now that the magic has been removed, and Django released 0.95, I decided to
> start porting my applications over. I knew the merge of magic-removal was
> coming, so I never deployed the apps. So, I decided to dump the tables that
>
Now that the magic has been removed, and Django released 0.95, I decided to
start porting my applications over. I knew the merge of magic-removal was
coming, so I never deployed the apps. So, I decided to dump the tables that I
had (there was no useful information in them) and start over. We
