Hi all.
I am in the midst of designing an ERD for a usage system. The management
would like to use name/value pairs to store the data since that would be the
most flexible. While I agree that it would be the most flexible on the
surface, I am concerned that it might not be a good idea. It is
Check the archives.
I think there was a long discussion on this topic not long ago.
Yechiel Adar
Mehish
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, July 09, 2002 6:38 PM
Hi all.
I am in the midst of designing an ERD for a usage
To: Multiple recipients of list ORACLE-L
@inter.net.il[EMAIL PROTECTED]
cc:
Sent by: rootSubject: Re: Name/Value pairs pros
You might compromise with a nested table of name/value
pairs for attributes to get management off your
back.
There was a lengthy thread a month or so ago on a
similar design issue. I am sure Tim Gorman can provide
some info on his nightmare project where there was a
single table w/name/value
How about Query performance will suck ?
Jared
Young, Jeff A. [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/09/2002 09:38 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Name/Value pairs pros
