"goff" <[EMAIL PROTECTED]> writes:
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?)
I have some cases where I want the exception. Those are more common when dealing with foreign keys and 1:1 relationships, though. For N:M there are much more cases where the CASCADE is desireable than anything else.
that I can't believe that SQLObject doesnt support this. Well, it does,
It is worse, in fact: it doesn't even raises an exception. It simply doesn't enforce the restriction at all and when you try to access the data from one side it fails while from the other side everything is perfect.
but only if I add a lot of boiler plate code to my model - something that I though SQLObject was designed to avoid?
-- Jorge Godoy <[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 -~----------~----~----~----~------~----~------~--~---
