Schemifier FK support uses incorrect JDBC API method (FKs generated every time)
See
http://groups.google.com/group/liftweb/browse_thread/thread/e3b10610e95e146
Looks like it should be using getImportedKeys, not getExportedKeys.
http://groups.google.com/group/liftweb/browse_thread/thread/e3b10610e95e146
Looks like it should be using getImportedKeys, not getExportedKeys.
Leave a comment
Posted diff to RB: http://reviewboard.liftweb.net/r/413/
(In revision:97d62d7e680e59a889ae7d60399005a9fb8149a5) Fix Schemifier FK Support to properly validate existing FKs
Closes #597
Changed Schemifier to use getImportedKeys, since we're looking
at FKs from the point of view of the referring table, not the
table that owns the PK.
Branch: master
Closes #597
Changed Schemifier to use getImportedKeys, since we're looking
at FKs from the point of view of the referring table, not the
table that owns the PK.
Branch: master
on 2010-10-12 16:54 *
By dchenbecker
Summary changed from Schemifier FK support uses incorrect JDBC API method to Schemifier FK support uses incorrect JDBC API method (FKs generated every time)