RE: DB layout - solutions needed

2004-01-16 Thread Tom Horstmann
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) > )

RE: DB layout - solutions needed

2004-01-16 Thread Tom Horstmann
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 (

Re: DB layout - solutions needed

2004-01-16 Thread Chris Nolan
" 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