Changes between Version 65 and Version 66 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Aug 7, 2006, 4:41:56 AM (18 years ago)
Author:
Malcolm Tredinnick
Comment:

Added note about constraint names causing reset problems

Legend:

Unmodified
Added
Removed
Modified

  • BackwardsIncompatibleChanges

    v65 v66  
    3434Changes made after Django [source:/django/tags/releases/0.91 0.91]
    3535 * May 1, 2006: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Removedthemagic Removed the magic]
     36
     37Changes made after Django [source:/django/tags/releases/0.95 0.95]
     38 * August 2, 2006: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Databaseconstraintnameschanged Database constraint names changed]
    3639
    3740== Moved mod_python handler ==
    … …  
    568571
    569572As of [2809], the [wiki:RemovingTheMagic magic-removal branch] has been merged. There's a LONG LIST of backwards-incompatible changes, and they're all documented on the RemovingTheMagic wiki page.
     573
     574== Database constraint names changed ==
     575
     576As of [3512], the format of the constraint names Django generates for foreign key references changed slightly. These names are only used sometimes, when it is not possible to put the reference directly on the affected column, so this is not always visible.
     577
     578The effect of this change is that {{{manage.py reset app_name}}} and similar commands may generate SQL with invalid constraint names and thus generate an error when run against the database (the database server will complain about the constraint not existing). To fix this, you will need to tweak the output of {{{manage.py sqlreset app_name}}} to match the correct constraint names and pass the results to the database server manually.
Back to Top