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
Currently, introspection over SQL adapter is a bit lacking. In some cases, we leak internal database structure that should not be visible to end users (i.e. schema edgedbpub) and in some cases we don't expose features because they don't exist in the internal database (foreign keys).
This issue is a tracking issue of all such problems:
defaults - some tools look at pg_attribute to see if a column is AUTO generated or not. We don't use PostgreSQL defaults, but inject the defaults in our compilation process. We should set column pg_attribute.atthasdef for those columns and populate table pg_attrdef,
Currently, introspection over SQL adapter is a bit lacking. In some cases, we leak internal database structure that should not be visible to end users (i.e. schema
edgedbpub
) and in some cases we don't expose features because they don't exist in the internal database (foreign keys).This issue is a tracking issue of all such problems:
pg_attribute.atthasdef
for those columns and populate tablepg_attrdef
,id
is not being picked up (by Django) as the primary key. Emulate introspection of primary keys over SQL adapter #7937FROM x JOIN y ON x.id = y.id WHERE id = 4
is not ambiguous (not really an introspection issue) Factoring of columns in USING clause over SQL adapter #7923The text was updated successfully, but these errors were encountered: