Well, in theory you cound use following select to show / list all foreign keys for some table together DDL of constraint definition. select att2.attname as "child_column", cl.relname as "parent_table", att.attname as...
Do you need to ensure that the same constraints across application are really the same? Use so called “domain”. It is public definition of constraint you can use repeatedly in whole application. Example is of for simplicity taken from PG documentation...
with recursive getall as ( select distinct ac.*, ac.table_name||'; ' as hierarchy, 1 as _level from allconst ac where dep_table_name is null --and table_schema='...your_schema_in_db...' --optional if you need to narrow select --and table_name='...your_table_name...'...
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRejectRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.