On 12/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Oops, put the first table schema with the code by mistake. > > Anyway, I realized I can work around this by explicitly specifying the > columns and foreign keys for just the association table, instead of > autoloading them. Then I can remove all the primaryjoin and > secondaryjoin stuff, and it works fine. But I still don't understand > why it didn't work the way I had it above - if anyone has any wisdom on > that I'd be very interested.
I don't have much wisdom to offer. But I'd be interested to know which version of ActiveMapper you are using, because I had the same problem as you: when I specified the primary and secondaryjoin option, it failed with the same error you cited. The only difference is that I don't autoload my tables but it doesn't seem to matter. The interesting part is that my problem was present when using version 0.2.8... But now I just updated my copy to the latest trunk and the problem magically disappeared. Cheers, Gaëtan. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
