pub fn declared(catalog: &Catalog, setting: &str) -> Vec<Relationship>Expand description
Every relationship declared for this catalog: the ones graph_links names, then one for each
foreign key a table was created with that the setting does not already name.
Section 2.5 of spec/graph/02-the-data-model.md lists the foreign keys first, as the path that needs nothing from the user, and the setting second, for data that arrived without constraints. The two are one list because nothing downstream cares where a relationship came from: the build verifies both the same way and a plan reads neither until it has.
A setting the parser refused contributes nothing, which is the silence rudb_links() has always
given one. A foreign key over no columns or into a table of another schema is left out.