Re: How to model searchable properties of an entity

Dilip Angal wrote:

> CELKO
Mind if I join?

> May be I did not clarify my problem.
> My business needs are I need to allow users to define attributes on
> the fly.

To me this suggests: for this requirement use searchable documents with tags, not tables. 'Attribute' has several meanings.

> This is not the DBA's fault.
>
> For e.g Part# 1001 has 20 attributes and part # 1002 has 10.
> User may choose to add 1 more to Part#20.

> That does not change the part entity. It only adds the attribute.
> If I do that I will have as many entities as number of parts I have in
> database.

> ABout your point, that data model is screwed is,.
> well that is my exact question. What should be the data model for this
> business neeed.
>
> In your own example, If I had 200 cars and each car having one or
> other attribute different than others, (different meaning, it is
> specified for one car but not for other) then I will end up with 200
> tables.
> In my case I have 100,000 parts. I will end up with 100,000 tables.

Model what you *can*, not what you cannot.

BTW could you please stop topposting? Received on Sat Aug 14 2004 - 10:05:25 CEST