Code

Changes between Initial Version and Version 1 of Ticket #18256, comment 8


Ignore:
Timestamp:
05/09/12 10:12:44 (2 years ago)
Author:
akaariai
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18256, comment 8

    initial v1  
    1 The problem is that when the table is created, Django wont touch it anymore. So, it will skip creating the foreign keys also. There is no schema migration capabilities in Django. 
     1The problem is that when the table is created in the first syncdb, Django wont touch it anymore in the second run. So, it will skip creating the foreign keys also. There is no schema migration capabilities in Django, and thus if table exists, it will be left alone in syncdb.