-
Notifications
You must be signed in to change notification settings - Fork 550
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use pg-specific schema tables for fkey detection
- Postgres doesn't care about names for uniqueness of keys unlike mysql because internally it keeps "oid" values to keep track of everything. Unfortunately this means that the information_schema standard is inadequate to differentiate between constraints that are named the same (which isn't possible in mysql, but is in pg). Hence we have to dip into the pg specific schemas for better or worse. - Fix naming of the sample schema in the README since it would fail for mysql due to duplicate naming. - Mark test schema up so we don't fix the bad names so we catch regressions here. - Fix #85
- Loading branch information
Showing
3 changed files
with
17 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters