Postgres entity generation support base tables.

[cooronx]

SeaQL/sea-orm#2412

I am researching how to implement this feature. and I found the problem was in sea-schema.

pub fn query_tables(&self, schema: DynIden) -> SelectStatement {
        Query::select()
            .columns(vec![
                TablesFields::TableName,
                TablesFields::UserDefinedTypeSchema,
                TablesFields::UserDefinedTypeName,
            ])
            .from((InformationSchema::Schema, InformationSchema::Tables))
            .and_where(Expr::col(TablesFields::TableSchema).eq(schema.to_string()))
            .and_where(Expr::col(TablesFields::TableType).eq(TableType::BaseTable.to_string()))
            .and_where(
                Expr::col(TablesFields::TableName).not_in_subquery(select_base_table_and_view()), // the child table intentionally removed here
            )
            .take()
}

the child table intentionally removed from this func. Was this designed intentionally? And what's the reason behind it?

[yuriy-yarosh]

@cooronx TLDR: table inheritance is bad, for multiple reasons. It's not a good practice, often breaks FK's. Current pg tuple routing for native partitioning impl completely omits it's use.

Just go for native partitioning and pg_partman, there are also some exotic things like temporal tables but their use cases can be obscure.

I would not expect this to be supported, or even worth supporting.