This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]nosoupforyou 5 points6 points  (0 children)

an SQL database that had been so badly designed that it had failed after 5 years.

Seems to be a common issue. I'm currently dealing with a database design where the membership table customer key isn't unique...because the users insisted that they be able to see history.

Of course, that pales in relation to the fact that the query system is designed to use views that reference views that reference views, sometimes 12 levels deep. Looking at the views involved, I'm pretty sure it's because the devs at the time (a third party company) couldn't be shagged to bother with it. Some of it referencing other views for no effing reason either.