Comment On tblStaffDirectory

Originally Posted At: http://weblogs.asp.net/alex_papadimoulis/archive/2004/05/20/136018.aspx [expand full text]
« PrevPage 1Next »

re: Your Daily Cup of WTF - tblStaffDirectory

2004-06-02 09:07 • by Darrel
Oh, my god. I nearly hurt myself reading this. You need to add a disclaimer...

re: Your Daily Cup of WTF - tblStaffDirectory

2004-06-02 19:07 • by steveaux
How about adding a column for data type and field length. Come to think of it there are a lot more attributes you could add too.

Works great as a standardized lookup solution though. I can't tell you how many times I have been annoyed by a database with a handful of core tables and about 50 lookups. All of them named pairs.

re: tblStaffDirectory

2004-06-12 22:59 • by Joe Celko
This #@$! nightmare is so bad it has a name --EAV (entity, attribute, value) design.

re: tblStaffDirectory

2004-06-25 06:12 • by Nick
this is the most creative table design i have come across

re: tblStaffDirectory

2004-07-23 15:27 • by Ben Adams
Of course, call me crazy, but couldn't you use systables and syscolumns?

I'm no BrainBench (tm) expert, but it just seems to me...

re: tblStaffDirectory

2004-08-09 08:49 • by Siva Mateti
This kind of design cannot handle "NOT NULLS" and other restrictions unless you write triggers on each column.

re: tblStaffDirectory

2004-08-11 16:46 • by Russ
Hey I have this great idea why dont we create a system that allows us to specify columns and tables and values for those columns. I even came up with a great name for it. I'll call it a database. And the best part is we can reimplement this "database" on a database. Then we can do it again. I mean seriously if your going to go through the trouble of doing this, why dont you just keep on going. Why not have a table that is tbl that has the same columns that define it for tblStaffDirectory. I mean you never know when we might want to add another column to tblStaffDirectory.

re: tblStaffDirectory

2004-10-06 04:19 • by Chris Brooksbank
I first thought hang on this is just a open schema - apparently this is a real technique. But then I looked at the column names and thought - No

re: tblStaffDirectory

2004-10-08 16:27 • by Aredridel
Whoa. That's like RDF without the tools to deal with RDF.

re: tblStaffDirectory

2004-11-15 13:52 • by Joe Hammer
We tried this once and ended up reproducing most of the syscolumns table... :)

Re: tblStaffDirectory

2006-07-05 23:05 • by Flex
protege.stanford.edu  uses exactly this strategy.

Re: tblStaffDirectory

2006-12-11 01:08 • by Simmo
Am I just being stupid here, or is this not just the data dictionary combined with the actual data?

metadata and data all in the same pretty little package... yeuch

Re: tblStaffDirectory

2009-11-13 21:03 • by DrJDX
My former employer's flagship software used a layout startlingly similar to this. It was made by outsourced developers, and now I think it's your fault.

I hate you.

Re: re: tblStaffDirectory

2010-02-17 20:09 • by Christian (unregistered)
299498 in reply to 22186
There's a lot more that's wrong with this design than a simple inability to handle "NOT NULL"s, honey.
« PrevPage 1Next »

Add Comment