On Jun 26, 2008, at 1:22 PM, [EMAIL PROTECTED] wrote:
> sort of, > x: relation( Foo, primaryjoin=, secondaryjoin=,remote_side=,whatever, > backref= halfbackref(name=abc,post_update=True)) > and let it construct the backref from relation.primary/secondaryjoin > etc, putting name and whatever extra args are there. it already re-uses primaryjoin and secondaryjoin in 0.5 with the regular backref="foo", reversing primary/secondary if both are present. the rest of the args dont really propagate. >> >> remote_side by definition cannot be the same on both sides of a >> relation. do you mean the backref should "figure it out" based on >> the forwards-facing explicit remote_side ? > yes, if there is explicit forward remote_side, the backward should be > guessable. if that needs extra info like pjoins etc, so be it. > heh, by definition... right now i'm giving same thing to both sides > and it seems to work. but not really sure, i havent tested heavily > the backref-using stuff. "usually guessable" is not really enough here. its definitely not "always" guessable. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
