This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Change constraint names to more meaningful names #84
Comments
List all constraints on database SELECT
tc.constraint_name, tc.table_name, kcu.column_name,
ccu.table_name AS foreign_table_name,
ccu.column_name AS foreign_column_name
FROM
information_schema.table_constraints AS tc
JOIN information_schema.key_column_usage AS kcu
ON tc.constraint_name = kcu.constraint_name
JOIN information_schema.constraint_column_usage AS ccu
ON ccu.constraint_name = tc.constraint_name |
After migration this is the end result
|
mithi
changed the title
Change foreign key names to more meaningful names
Change constraint names to more meaningful names
Nov 3, 2020
mithi
added a commit
that referenced
this issue
Nov 3, 2020
Change constraint names to more meaningful names For more information see : #84 Fix: setup script (install first before anything else) Improve logging when seeding database tables
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the foreign key is not readable IE
The text was updated successfully, but these errors were encountered: