[sqlalchemy] Re: PostGreSQL Referential Integrity with composed primary key

2007-02-15 Thread dischdennis
Sorry, I placed the testcase here: http://groups.google.de/group/sqlalchemy/web/testcase_dischdennis_Postgre.py I could not find a way to upload it with the message directly. Dennis --~--~-~--~~~---~--~~ You received this message because you are subscribed to

[sqlalchemy] Re: PostGreSQL Referential Integrity with composed primary key

2007-02-15 Thread Gary Bernhardt
The pr_PurchaseRequisition_has_CELLS_budget_has_CELLS_costCenter table is the one that's causing your problem. It has a foreign key to CELLS_budget_has_CELLS_costCenter.CELLS_budget_ID (and another to CELLS_costCenter_ID on the same table). Neither of those two columns are unique. If you add

[sqlalchemy] Re: PostGreSQL Referential Integrity with composed primary key

2007-02-15 Thread Gary Bernhardt
On 2/15/07, dischdennis [EMAIL PROTECTED] wrote: Thats the problem. I know that it is possible to add unique = True for each column. But then it is not possible to assign combinations of budget / cost centers like (1,1)(1,2)(1,3)...etc... So I would like to define both primary keys, the