 | |
#41
 
| |||
| |||
|
Re: Modeling question... -
07-25-2008
, 09:05 AM
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#42
| |||
| |||
|
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#43
| |||
| |||
|
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#44
| |||
| |||
|
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#45
| |||
| |||
|
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#46
| |||
| |||
|
|
Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htm and didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) |
requirement. I think it's different from "I am too lazy to do a proper data
model". There are plenty of "normal" attributes left to model ERD like.
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
#47
| |||
| |||
|
|
Bob Badour schrieb: Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/ea...ontents.htmand didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) But "we want to be able to create and delete attributes" is a customer requirement. I think it's different from "I am too lazy to do a proper data model". There are plenty of "normal" attributes left to model ERD like. Lots of Greetings! Volker -- For email replies, please substitute the obvious. |
#48
| |||
| |||
|
|
Bob Badour schrieb: Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/ea...ontents.htmand didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) But "we want to be able to create and delete attributes" is a customer requirement. I think it's different from "I am too lazy to do a proper data model". There are plenty of "normal" attributes left to model ERD like. Lots of Greetings! Volker -- For email replies, please substitute the obvious. |
#49
| |||
| |||
|
|
Bob Badour schrieb: Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/ea...ontents.htmand didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) But "we want to be able to create and delete attributes" is a customer requirement. I think it's different from "I am too lazy to do a proper data model". There are plenty of "normal" attributes left to model ERD like. Lots of Greetings! Volker -- For email replies, please substitute the obvious. |
#50
| |||
| |||
|
|
Bob Badour schrieb: Ooooh! Reinventing EAV with levels... Possibly. I had a look at http://ycmi.med.yale.edu/nadkarni/ea...ontents.htmand didn't find anything exciting. All my attributes (key value pairs) are (for the purpose of this discussion) strings, so the Data tables hierarchy ends with EAV_Objects in the first image of that link. My problem is that, that I haveTest three different "Objects_1" tables and I'd like to avoid having to replicate the EAV_Objects-Table for each "Objects_1"-Table. OTOH, I could have the "level" entities all be children of an id table and put the key value pairs into a child of that table. I need to try this out. Thanks for providing the pointer! Volker Just to be clear, I was more than offering a pointer. I was also ridiculing the idea of EAV. I got that. :-) But "we want to be able to create and delete attributes" is a customer requirement. I think it's different from "I am too lazy to do a proper data model". There are plenty of "normal" attributes left to model ERD like. Lots of Greetings! Volker -- For email replies, please substitute the obvious. |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.