On 8 Oct 2008, at 09:22, Francis Fish wrote: > On Wed, Oct 8, 2008 at 6:43 AM, Peter Morris <[EMAIL PROTECTED] > > wrote: > > database level constraints are BAD. > > Don't say something like that when I'm trying to drink my coffee. > > I half agree with you, because rspec'ing up things for child > entities can be a total pain. On the other hand, identifying how you > ended up with a load of orphaned data without constraints is very > difficult. If you had constraints turned on then the orphan wouldn't > have happened. >
Ok, but think about how you got those orphans... you deleted parents, without cleaning up. ok fine, but the constraint is not FIXING things, it is HIDING things. Those missing orphans where possibly your only clue that something might be structurally wrong in your models. but the constraint is hiding that information from you. Don't use constraints to catch sloppy models. > The middle way between extremes is usually best. > > I also agree that my newer rails apps have very few constraints in > them, but some are necessary. So maybe I'm agreeing with you after > all. I think it would be useful for training to have the discussion > and let people think it out for themselves. Although most of the > Java crew don't get relational databases and that's what I like > about Rails - it does. > > F > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" 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/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
