NERDRAGE - DataBase Design
Posted: 18 Feb 2010, 14:36
Oh ffs:
There are a host of nitpicky little validation rules that don't serve to improve the quality of the data contained, but do serve to make our lives a true hell whenever a user's input is slightly at odds with what the DBA had in mind.
Also, there are spelling errors IN THE FIELD NAMES.
Most of the DBs we come across have been poorly designed, but this one takes the cake.(11:27:40 AM) Self: so this database we're writing software for
(11:27:45 AM) Self: has validation for the fields
(11:28:08 AM) Self: you know - stuff like, you can't put a driver's dob in that would make them younger than their years of driving experience
(11:28:27 AM) Self: except there's a field here for year of manufacture for a car
(11:28:40 AM) Self: and the validation rule is:
between 1979 and 9999
(11:28:58 AM) Self: so okay, NOBODY is going to be driving a car older than 1979 - that's PREPOSTEROUS
(11:29:16 AM) Self: and we'd better plan for this database to still be in use when people are driving cars in SEVEN THOUSAND YEARS TIME
(11:29:18 AM) Self: ffs
(11:29:44 AM) Constance: HAHAHA
(11:29:50 AM) Constance: that's sort of awesome in a retarded kind of way
(11:30:10 AM) Self: gotta give the DBA points for thinking about longevity
(11:30:29 AM) Self: but what happens when it clocks over to the year 10000, DBA?
Did you think about that?
(11:30:44 AM) Constance: it'll be Y10k
(11:30:45 AM) Constance: yikes
(11:30:48 AM) Self: THE WHOLE COMPANY WILL FAIL BECAUSE YOU DIDN'T PLAN FOR THE Y10K BUG
There are a host of nitpicky little validation rules that don't serve to improve the quality of the data contained, but do serve to make our lives a true hell whenever a user's input is slightly at odds with what the DBA had in mind.
Also, there are spelling errors IN THE FIELD NAMES.