Ivan Nastyukhin wrote in post #974793: > On Jan 14, 2011, at 12:23 AM, Marnen Laibow-Koser wrote: > >> Please quote when replying. >> >> Chris Habgood wrote in post #974782: >>> Maybe so but you do not have to 3rd level normalize EVERY thing in a db. >> >> Yes, you absolutely *do* have to normalize at least to 3NF. The only >> excuse for a denormalized schema is if you've actually *measured* that >> you've got a performance bottleneck that denormalization will solve >> (note: in 11 years of Web application development, I've never once had >> to do this). > > i think 11 years create u too old school...
And I think you don't know what you're talking about. > 3fn in web development? our > dude, so if u like problems -)) 3NF *solves* problems. What problems do you think it creates? > if u use rails, ar- pattern, thinkin in models, not in database schema. > + counter_caches columns (helpfull in development) No! When working with SQL databases, you have to understand and work *with* the database. When working with objects, you have to understand and work *with* the objects. Fortunately, AR lets you do both simultaneously if you know what you're doing. And counter_cache should be considered a cheap performance hack, nothing more. It's not necessary from a design standpoint if your data model is correct. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
