Closed GoogleCodeExporter closed 8 years ago
Good catch.
Some clarifications:
- The problem has nothing to do with foreign keys
- Has nothing to do with name of the column
- Comes from a UNIQUE KEY on a NULLable column, where all values are indeed NULL
Solution is to:
- prefer not-nullable keys to nullable keys
- prefer PK over "normal" keys on similar data types (also implies the above)
Original comment by shlomi.n...@gmail.com
on 19 Mar 2013 at 8:25
Here's an immediate fix to the _split_generate_dependency_tables() routine;
will incorporate with next release.
Solves the example with the "film" table. Let me know if also solves the
problem you describe in your blog.
Original comment by shlomi.n...@gmail.com
on 19 Mar 2013 at 8:38
Attachments:
This issue was closed by revision r442.
Original comment by shlomi.n...@gmail.com
on 20 Mar 2013 at 8:03
Yes, this resolves the problem as originally reported on my blog.
Thanks!
Original comment by ike.wal...@flite.com
on 27 Mar 2013 at 8:30
Original issue reported on code.google.com by
ike.wal...@flite.com
on 19 Mar 2013 at 5:21