From: Nick <ni...@dd...> - 2003-04-29 17:40:27
|
On Tue, 2003-04-29 at 12:05, Luke Opperman wrote: > This is not SQLObject specific, but I guess I've never understood the > "tablename_id" argument for making joins cleaner. in SQL: > > ".... ON person.id = other.person_id...." vs > ".... ON person.person_id = other.person_id" try USING (person_id) instead. > So yeah. Not sure what my point is, > except I'll assume the new Style object ought to cover this, and > that's that. I looked at that, and I think it's a step in the right direction, but it needs to be fleshed out a little more I think. > The problem (that i've experienced) is circular *import* dependencies. > I would agree, strings seem to solve this. With caveats mentioned in > another mail about joined/FK'ed classes possibly needing to be > imported by a third-party class that doesn't want to have to know > that Person has a Phone object (and hence where to import Phone > from), just that Person.phone returns a Phone object. As long as you make your classes part of a module, I don't see this being a problem, since the class names are all stored up when you define the class, which will happen whether you import 1, 2, or all the classes in a module. Nick |