Wyatt Lee Baldwin wrote: > >> Anyway the primaryjoin here looks fine and does >> represent the same thing you're getting in your route() @property. >> It's >> a simple many-to-one with an additional criterion. Nothing needs to be >> configured in the database as far as foreign keys, configuring it as >> such >> within the table metadata is all SQLA cares about. > > I'm still not clear if/how I can replace the property with the > relation. When I use the relation shown above, I get the big join. > Sorry if I'm being daft.
what big join ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
