a database table can only have one primary key (hence "primary"), but that key can contain more than one column (a "composite" primary key).
the model you have here is a little unclear, did you mean for the primary key of Exchange to be "exchange" , and the primary key of PhoneNumber to be the composite of "exchange" and "phone number" ? that would be my guess as to what you're looking for. On Mar 6, 2013, at 6:05 PM, Randall Degges <[email protected]> wrote: > Hi all, > > I'm having a lot of trouble figuring out how to properly build my ForeignKey > column for a table I'm defining. I've outlined my models here: > http://pastie.org/6407419# (and put a comment next to the problematic line in > my PhoneNumber model). > > Here's what's happening: > > My Exchange table has two primary keys. This is required for my use case. > > The PhoneNumber table I'm trying to define needs a ForeignKey to the Exchange > table, but since the Exchange table has two primary keys, I can't figure out > how to make the relationship work. > > Any guidance would be appreciated. Thank you. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
