On 23/02/2012 13:05, Michael Bayer wrote:
We only have a recipe where we assume INHERITS is used like the PG docs say in
http://www.postgresql.org/docs/9.0/static/ddl-partitioning.html#DDL-PARTITIONING-IMPLEMENTATION
. That is, child tables don't have any extra columns.
In this scenario, SQLAlchemy doesn't need to know about the child tables at
all, pretty much.
Here's the recipe:
http://www.sqlalchemy.org/trac/wiki/UsageRecipes/PostgreSQLInheritance
*nods*
So I guess if I actually want to map a child table, I just need to do it
myself?
SQLA has no facilities to reflect the INHERITS clause itself.
Okay, but if I reflect with I get all the tables, parents and children,
or just the parent? (I'm hoping for the former ;-) )
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
