David Fetter wrote:
>> I think the main discussion has been around:
>> 1. Whether Edward's final-year project is basically EAV (in which case
>> he'll probably need to work hard to get good marks).
>>
>
> As Josh mentioned, I'm on of the people who says EAV is never
> justified. We do have a way of expressing wide ranges of constraints
> not known in advance: it's called SQL, and people need to do some
> design using it, however much they may fear that they've left
> something out somehow. :)
>
>
ISTM that the biggest problem with EAV is that is is far too seductive,
and allows for lazy design (or lack of design). There might be odd cases
(pace David) that require it, but I strongly suspect in most cases it is
not necessary.
Perhaps we need some sort of discriminant record type ;-)
cheers
andrew
