Thanks J. The more people comment here, the more confortable I feel about our current approach. Albeit not perfect, I'm pretty sure we're in the right direction. And yes, we're upping the Unit Tests lately, which I've banged on about loads, and 'time' is finally being properly allocated to it from the 'time' people.... Thanks J

PIEBALDconsult wrote: Perhaps you could explain how it would implement the automatic translation/look-up without performing a JOIN behind the scenes? There is no look-up with an ENUM data type. It's just a data type. Instead of using a number with no inherit value, with no referential data checking for a rogue number, etc. you can use strings. Not only is there no look-up, which is fast, this has so many advantages with automatic data checking / integrity (even in the case of a tri-state Boolean) it's unreal. PIEBALDconsult wrote: You appeared to not know what I meant. I did. And like I said, ENUM types fall short on variable length rows of values / types / whatever you want call them. And if the look-up needs to be re-used they fall short. But for a one-time small item, such as tri-state Boolean they're awesome. PIEBALDconsult wrote: I think we are now. I've always been talking about this yo. Jeremy Falcon

I don't know what I haven't told you .... yet.... :)