I'll look into "a)" do the mappers pick up foreign key constraints and the polymorphic/inherited details from the metadata when their created or do you have to specify them? - As a last resort i can query the data dictionary.
Question 1 >From the sqlalchemy mapper configuration, PostGreSQLs version of inheritence sounds like the "concrete" variary, as it automatically joins the tables together with a select unless you use "FROM ONLY table_name" Concrete table inheritance : where each type of class is stored in its own table joined table inheritance : where the parent/child classes are stored in their own tables that are joined together in a select Can someone confirm which category postgresql falls into? Question 2 Does the metadata.reflect stuff reflect inherited table definitions from PostGreSQL? Question 3 The inheritence i was refering to is present in postgresql CREATE TABLE table1 ( col1, col2 ); CREATE TABLE table2( col2, col3 ) INHERITS table2; I want to find out that : * table2 is inherited from table1 * table2.col2 definition is from table1 and from table2 (postgres merges them) * table2.col1 definition comes from the inhertance of table1.col1 (much the same as the line above) Does sqlalchemy support this distinction? Can i get the details from somewhere? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
