>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. This way you won't declare the reference twice, plus it is essential if you ask SqlAlchemy to do your cascading deletes. I agree with your general concern, though -- SqlAlchemy is super powerful and a great tool, but I have seen many situations where if you do something OBVIOUSLY wrong it lets you shoot yourself in the foot. No error message, just patently incorrect behavior. I hope to see this improve in the future. Barry __________________________________________________ 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 -~----------~----~----~----~------~----~------~--~---
