Commit failing test for unique constraints: When a table has two or more unique
authorDaniel Westermann-Clark <danieltwc@cpan.org>
Fri, 7 Jul 2006 05:30:53 +0000 (05:30 +0000)
committerDaniel Westermann-Clark <danieltwc@cpan.org>
Fri, 7 Jul 2006 05:30:53 +0000 (05:30 +0000)
commit365d06b716eb2b3894d83291c612b116ade1e9d7
treeed83e91a303b796fe36d5be9eb4521c8d20ed1a5
parent98ba74b42c19f817bd58641a018b4bd1320d66cf
Commit failing test for unique constraints: When a table has two or more unique
constraints, and you satisfy one, you get a partial key in the WHERE clause.

This required adding two unique constraints to the 'track' table, and fixing up
a couple of cases where we had duplicate values.
t/60core.t
t/66relationship.t
t/80unique.t
t/lib/DBICTest/Schema/Track.pm
t/lib/sqlite.sql