|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 9:43 AM
Points: 1,137,
Visits: 670
|
|
Okay, so you're saying that some OO devs designed this database like they would design an OO system? I've seen some absolutely --wonderful-- output from those situations. Confusion about is-a vs. has-a relationships and how the DBMS enforces such relationships. In one case, an online ordering (ecommerce) system was designed such that the products table had a foreign key to the line items table! End result: These guys were inserting fake orders every time they wanted to sell new products. And of course, there were duplicate products inserted with every order. Luckily, their volume was very low
-- Adam Machanic SQL Server MVP SQLblog.com: THE SQL Server Blog Spot on the Web
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 8:38 AM
Points: 1,032,
Visits: 390
|
|
David: I would hope that I haven't built quite that bad of a reputation for apoplexia! I admit that I do tend to respond to certain topics rather forcefully, but that is because I've seen too many systems just like the one you and Adam describe, and it annoys the hell out of me when I have to clean up the mess. I have often likened a job like that to trying to separate the toilet paper out of the sewage; at best it's a nasty, difficult job, at worst it's a nasty difficult job that also happens to be impossible. Then to hear (or read) someone put forth this kind of "solution" as "elegant" just makes me want to wring their neck... To anyone reading this: Relations (db tables) <> OO Objects!!!!! Don't make that mistake, they are not even close to being the same thing. This is what C.J. Date called the "First Great Blunder" which Adam and I have discussed before...
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
I actually agree with most of the things you say, possibly with the exception of the separating out toilet paper from sewage.
When ever I see a badly designed database supplied by a 3rd party organisation I get the warm glow of job security. If every database I saw was well built and well designed then what would people need me for?
LinkedIn Profile
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 8:38 AM
Points: 1,032,
Visits: 390
|
|
Job security is nice, but in my experience, there are too many truly productive things that don't get done because so much effort goes into supporting junk systems. I'm much more valuable to my company when we are actually swimming toward a goal as opposed to struggling to tread water. Ultimately it's my value to the company that determines how secure my job is.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
|
|
|
|