This endeavor has talked about high normal form on multi-processor/core/SSD machines from the beginning. On occasion, the complaint that such "complicated" schemas are not practically updatable, given existing client code, comes up. One hears this from Agile Zealots, who still want to write dumb data/smart code just as their granddaddies did. My answer has always been that "real" base tables are hidden, with the named "tables" being views. Updating, through joins for example, is handled with stored procs.
Turns out that SQL Server, at least, implements triggers which get around the updatable view problem.
Michael Swart talks about it.
But When Would I Use This?
I thought of the perfect use case. This strategy helps with SCHEMA REFACTORING.
With the I/O capability of these current machines, the cost of maintenance drops considerably. Think of it as OO inheritance for databases. Or as Bill Gates was famous for saying (he did, didn't he?), "let the new hardware fix it".
No comments:
Post a Comment