lack of check about the value to use for existing columns at migration

[mozgurbayhan@…]

With sqllite db, south can take any value e.g(datetime.date.today()) as a foreign key value that can couse db corruption.

[andrew]

SQLite does not have any integrity checks for that - this is a problem with SQLite, not with South (other databases will raise this error at the database level), so marking this WONTFIX.

[mozgurbayhan@…]

Is it hard to do that check at application layer?

[andrew]

Yes, because we'd need to write code which reversed the foreign key constraint, obtained the field at the other end, and then tried to run the values through that (and even then that wouldn't catch all cases).

The default value used for existing columns is entirely manually specified, so we've made the fair assumption that you know what you're doing instead of complicating the codebase even further. South _could_ contain all manner of checks to prevent even the simplest of mistakes, but then it would be even bigger, more complex, and more unmaintanable.