Re: How to model searchable properties of an entity

From: Bernard Peek <bap_at_shrdlu.com>
Date: Thu, 19 Aug 2004 11:40:53 GMT
Message-ID: <GXRUQf9QJIJBFwXx_at_shrdlu.com>


In message <cg1fa1$52m$1_at_voyager.news.surf.net>, pstnotpd <schoenmakers_at_tpd.tno.nl> writes
>--CELKO-- wrote:
>>>>The entity-attribute-value system is an alternative but I don't
>> believe it is much better, and I speak as one who has built such
>> systems. You still need every user to have pretty much the same
>> training as a DBA. If you can't ensure that all of your users are of
>> that calibre then the system will rapidly become unworkable. <<
>Why? As I understand it the point of EAV is to build the user interface
>to represent the logical data model. You wouldn't expect 'users' to
>query directly on the physical model would you?

He was quoting me there. The point of EAV is to build a database without a logical data model. You don't need one to build an EAV system.

It reminds me of the C language.

The greatest advantage of the C language is that in the hands of a competent programmer it can do anything.

The greatest disadvantage of the C language is that in the hands of an incompetent programmer it can do anything.

-- 
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.
Received on Thu Aug 19 2004 - 13:40:53 CEST

Original text of this message