I cant run the generator since theres a dependency "Config" not found, but the standalones are using the "foreignkey" parameter which is both deprecated and also more or less mutually exclusive with "remote_side".
the trunk now has the "foreign_keys" parameter which behaves consistently as a list of foreign key columns in the join conditions. But, you dont even need that since your Table objects already have the correct ForeignKey objects in them. anyway "foreignkey" is apparently not fulfilling its legacy behavior so ill try to fix that, but if you use foreign_keys (or nothing) for now itll work. 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 [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 -~----------~----~----~----~------~----~------~--~---
