You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That means we can have many parents for one child table which make the concept of the PG table inheritance confusing ;-)
If we create table which have many parents, then we will have SQL error with schemainspect: more than one row returned by a subquery used as an expression
I added LIMIT 1 to line 43 to see if this improves the situation, and I am getting reasonable results - all inheritance I have is experimental, so I don't mind.
From the PG docs: A table can inherit from more than one parent table, in which case it has the union of the columns defined by the parent tables.
That means we can have many parents for one child table which make the concept of the PG table inheritance confusing ;-)
If we create table which have many parents, then we will have SQL error with schemainspect:
more than one row returned by a subquery used as an expression
schemainspect/schemainspect/pg/sql/relations.sql
Line 43 in 066262d
I would propose returning array of parent tables, but not sure if that is supported by the rest of the
schemainspect
Here is the problematic SQL:
schemainspect/schemainspect/pg/sql/relations.sql
Line 37 in 066262d
You can use
or
and probably even
But you may want to set quote_all_identifiers to ensure that all names are always quoted with
"
.The text was updated successfully, but these errors were encountered: