Yes, even an arbitrary rule is fine as long as you're consistent. Just watch out when you rename a table. :-)
When I first started working with SqlAlchemy I wrote some automated checks to detect certain problems that kept tripping me up. You could do something similar for duplicate relations. Barry ----- Original Message ---- From: Ben Sizer <[EMAIL PROTECTED]> To: TurboGears <[email protected]> Sent: Wednesday, October 24, 2007 5:10:23 AM Subject: [TurboGears] Re: How to choose between Elixir and plain SQLAlchemy On Oct 24, 1:23 am, Barry Hart <[EMAIL PROTECTED]> wrote: > >unpleasant, for 2 reasons: firstly, because of the unintuitive backref > >stuff which seemed to allow a reference to be accidentally declared > >twice under different names, and secondly because it specifies the > > I have learned you always want to declare the relationship on the parent object of a relationship. And what about situations where there is no parent? :) I suppose I could just put it on the one that came first in the alphabetical order...! A lot of my objects aren't in some sort of composition hierarchy but are actually just loosely associated, and that can make it a bit awkward to decide where to put the links. Oh well, it's not insurmountable. -- Ben Sizer __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
