we've had a lot of issues with Postgres and using information_schema. whereas MySQL's information_schema support was pointless, Postgres mostly works, but performs very slowly unless you VACUUM your database every hour. we've had reports of primary keys not being reflected for tables across user names as well.
what does the list think of dumping information_schema usage altogther and using PG's own schema tables for reflection ? On Jun 3, 2006, at 4:41 AM, Yuan HOng wrote: > There is something wrong with my 7.3.x database. The primary key is > not shown in information_schema.table_constraints while it is in the > table definition. > > So this is not a bug of SA but maybe that of postgres. > > On 6/3/06, Yuan HOng <[EMAIL PROTECTED]> wrote: >> I've found out that when I try to autoload the table metadata from >> Postgres 7.3.x databases, the primary key column is not correctly >> detected by SA. The loaded table will be without primary key. >> >> But with Postgres 8.x, primary key is correctly set for the table >> automatically reflected from the database. >> > > -- > Hong Yuan > > 大管家网上建材超市 > 装修装潢建材一站式购物 > http://www.homemaster.cn > _______________________________________________ > Sqlalchemy-users mailing list > Sqlalchemy-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
