Re: [sqlalchemy] ForeignKeyConstraint with composite keys doesn't throw appropriate exception with multiple tables

2012-04-03 Thread Michael Bayer
On Apr 2, 2012, at 8:39 PM, Robert Rollins wrote: > However, I didn't notice until some time later that there's a serious > bug in my ForeignKeyConstraint definition: the 'refcolumns' argument > isn't referring to columns within the same table. Rather than > ['account.account_name', 'contact.id'

[sqlalchemy] ForeignKeyConstraint with composite keys doesn't throw appropriate exception with multiple tables

2012-04-02 Thread Robert Rollins
While I was writing up a many-to-many relationship between tables where one has a composite primary key, I ran into problems that initially prompted me to start writing this post. Here's my original code that was giving the confusing error about which I originally began writing: class AccountSync