yeah actually "foreignkey"'s legacy behavior is fine, those examples are using it exactly incorrectly....the parameter takes on a different meaning when used in a self-ref relationship (thats why its been replaced) - its synonymous with "remote_side" in a self-ref relationship.
On Feb 20, 2007, at 4:39 AM, svilen wrote: > something with lazy-relations, self-referential, but pointing to > another instance, not to _itself_. Happens regardless of inheritance. > > 2308 is all-ok, 2344 is same as 2309. > > hmm, what should i do to this all-combination test, so it gets > included it in the testsuite? i.e. make it unittest-like but keep the > other functionality somehow... > i may not be around to run it once a month... > > run sa_ref_A_B_A_all.py generate=failed,one (needs sa_generator.py) > > or (just first one) > test_AB_poly_0__inh_None__Alink_None__Blink_B1__BAlink_None__Alazy__Bl > azy.py > + sa_gentestbase.py > > ciao > svil > > > > <sa_generator.py> > <sa_ref_A_B_A_all.py> > <test_AB_poly_0__inh_None__Alink_None__Blink_B1__BAlink_None__Alazy__B > lazy.py> > <sa_gentestbase.py> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
