Re: How to model searchable properties of an entity
Date: Mon, 16 Aug 2004 09:29:02 -0400
Message-ID: <e6Kdnaa1ydOCK73cRVn-tg_at_comcast.com>
"Dilip Angal" <dilip_angal_at_yahoo.com> wrote in message
news:df683587.0408151804.e7bbb5a_at_posting.google.com...
> I still don't know how to convince you guys.
> You are all pointing to the process issues that users may give
> different spellings for color.
> I can handle that part by having an admin to create the properties who
> makes sure that the property being added to the part is really
> required and is not used in past by any one in any different context.
>
Thank you for clarifying the issues.
By "admin", do you mean a DBA?
If so, I agree with you that that's the person who should control traffic, and add new properties when they are needed, and are not old properties in a new disguise. Having this under a DBA's control is better than having it under the application programmer's control, the users' control, or out of control.
The question is how is it best to exercise this control?
> But the basic fact does not change.
> I need to keep adding these properties from time to time because user
> communitiy can not decide all of them upfront.
It gets worse. A year and a half down the road, performing useful queries on this data is going to be like looking for the body of a murder victim in a landfill. The container wasn't built with that kind of search in mind. Received on Mon Aug 16 2004 - 15:29:02 CEST