Jorge Godoy wrote:
One alternative is defining the mappings yourself instead of letting SO create them. This is a common approach when you want to add extra data to this "pair".
That's what I did in the end. It's just that I think that having a cascading delete on a related join is so commonplace (actually, I cant think of a situation where I didnt want a cascade - who would want to have user.groups throw an exception just because i removed a group?) that I can't believe that SQLObject doesnt support this. Well, it does, but only if I add a lot of boiler plate code to my model - something that I though SQLObject was designed to avoid?
best regards, mfg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
