Hi Michael, I had the same problem for a while. I'm not exactly sure what I did in order to fix this (have 2 ideas in my mind, need to figure out which of it it was). As soon as I remember, I'll let you know.
On Aug 29, 1:44 am, Michael Brickenstein <[EMAIL PROTECTED]> wrote: > Hi! > Hi have a similar problem using > table reflection a la sqlsoup. My DB Backend ist postgresql 8.3. > > I have a many to many relation: > orms5=# \d project_programming_language > Table "public.project_programming_language" > Column | Type | Modifiers > -------------------------+---------+----------- > project_id | integer | not null > programming_language_id | integer | not null > Indexes: > "projprogpkconstraint" PRIMARY KEY, btree (project_id, > programming_language_id) > Foreign-key constraints: > "programmierspracheconstraint" FOREIGN KEY > (programming_language_id) REFERENCES > programming_language(programming_language_id) ON DELETE CASCADE > "projektconstraint" FOREIGN KEY (project_id) REFERENCES > project(project_id) ON DELETE CASCADE > > I got the same message, when delete an object of the table > programming_language: > > Dependency rule tried > to blank-out primary key column > > As you can see, the foreign key constraints in the db work fine: > I can drop the row via a > DELETE > statement in sql. > > Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
