Confessions of an IT Manager_Phil Factor
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
When the Fever is Over, <strong>an</strong>d one's<br />
Work is done<br />
First published 29 May 2008<br />
Like the mumps, 'EAV' disease strikes the afflicted<br />
only once, but the memories <strong>of</strong> suffering <strong>an</strong>d delirium<br />
last forever.<br />
There comes a time in the life <strong>of</strong> <strong>an</strong>yone working with databases when they<br />
are struck with a peculiar mental aberration. For w<strong>an</strong>t <strong>of</strong> a better term, it is<br />
usually called 'One True Lookup Syndrome' or OTLS. It is in the same league<br />
as the rather more severe affliction 'EAV disease' (Entity Attribute Value). It is<br />
like measles or mumps in that it afflicts the sufferer just once <strong>an</strong>d he, or she, is<br />
thereafter immune. The memory <strong>of</strong> the suffering <strong>an</strong>d delirium is retained,<br />
however, <strong>an</strong>d the feelings <strong>of</strong> embarrassment.<br />
The sufferer is easy to recognise. He shakes his head in wonder,<br />
saying "This is like, such a cool idea, how come nobody has thought <strong>of</strong><br />
it before? It is like wow! I me<strong>an</strong> it is so neat." A classic symptom <strong>of</strong> the<br />
disease is that they will sidle up to you <strong>an</strong>d ask how to patent s<strong>of</strong>tware<br />
ideas. We grey-muzzles will shake our heads sadly, with a pitying<br />
smile, <strong>an</strong>d just mutter solemnly 'One true lookup table'.<br />
Usually, OTLS comes about when one is forced to create a number <strong>of</strong><br />
simple lookup tables which contain a code <strong>an</strong>d a name. One gets the sudden<br />
flash <strong>of</strong> inspiration that one could roll them all into one lookup table, with a<br />
unique identifier for each row, <strong>an</strong>d a type field, thereby saving the chore <strong>of</strong><br />
creating <strong>an</strong>d maintaining a number <strong>of</strong> tables. EAV disease, like OTLS, both<br />
tend to be the result <strong>of</strong> pressure from programmers to push their OO designs<br />
back into the relational database. There is loose talk <strong>of</strong> 'persisting object data in<br />
a data store', as though one was storing apples in a shed. It also comes about<br />
when a development team attempts <strong>an</strong> 'Agile' development before they've fully<br />
understood the data model.<br />
I'm a recovering EAV sufferer <strong>an</strong>d I remember the first symptoms well. I<br />
was under stress, working with a systems <strong>an</strong>alyst whose <strong>an</strong>alysis skills were at<br />
about the same level as a dead sheep's. The database was for <strong>an</strong> internet system<br />
for car dealerships, selling second-h<strong>an</strong>d cars. It was supposed to value your<br />
stock, <strong>an</strong>d to enable groups <strong>of</strong> dealers to supply a punter with the exact car he