Actually, I did understand, I just didn't explain myself properly. The process for managing relations between your mapped objects is precisely the same as managing relations between objects that do not get mapped. All of the same pitfalls, all of the same benefits, all of the same restrictions.
Put another way: You are already right about this: On Thu, Jan 21, 2010 at 4:30 AM, werner <[email protected]> wrote: > I liked how it is shown in the tutorials to have one module.tableX.py file > per table, if one does this then one would have to import "C" in both the > "A" and "B" file and "B" would also needed to be imported in "A". > > Besides not doing any circular imports is there anything else one has to > watch out for? > Since these are Python objects, you would only watch out for the same things as with regular Python objects (which is another way of saying "I can't think of anything else to watch out for). -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected]--
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
