Hi Brad,
> create table entity (
> ent_id number primary key,
> ent_namevarchar(50)
> );
>
> create table nameval (
> nv_id number primary key,
> nv_ent_id number,
> nv_name varchar(50),
> nv_val varchar(50)
> )
Thanks Chris,
> Will you have an object hierarchy of any type to speak of?
no hierarchy, they're all roots.
> Which language are you looking at building this funky thing
> in? If it's
> Java or C++, you might want to look at persistant object
> stores that are
> specifically for this purpose (
"
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Hmm
Will you have an object hierarchy of any type to speak of? If so, you
should be able to factor quite a few things out, but then you're going
to have the problem that objects further down the tree will take longer
Hi all,
i want to store an unfixed number of object-characteristics
of an unfixed datatype for 1-8000 objects. Data is mostly
read, rarely written. Is there an quite optimal table-structure
for that?
If i use one table for all characteristics i need as many
columns as there are datatypes used. On
