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 unique=True to both of their definitions, SA will succeed in creating the tables. It will fail later, though - you apparently insert rows where those columns really aren't unique.
On 2/15/07, dischdennis <[EMAIL PROTECTED]> wrote: > > > 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 the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
