> by lookups in the db? sounds like your trying to turn your relational
> database into an object-oriented data storage!
i am
> remember that this is exactly what java will do for you behind the
> scene. use the built-in language features instead!
probably will once familiar (new to ejb)
> > The only case I foresee in which it will be desirable to have fully
> > "flattened" classification (so that SQL can do all the manipulation and
> > transformation) is for reporting. For such cases - batch style tasks
> > that
> > process *all* the data - I see no problem with preprocessing the
> > implications of THINGCATEGORY into a FLATTHINGCATEGORY table.
flattening - dynamically resolving simple list of all applicable categories
direct + imherited
FLATTHINGCATEGORY table because no temp tables in Interbase
> i hope you don't think i suggested a flat classification structure.
no
> what i wanted to convey was this: your problem can be easily and
> effectively modelled with object-oriented inheritance and polymorphism (in
> fact what you're talking about is a text-book oo example!)
yes
> but mapping it
> cleanly onto a relational database is next to impossible.
yes
> have you considered other alternatives for data storage?
no
> anyhow, if you have to choose between corrupting your design and a
> convoluted db structure - well, i think you see which way i'm leaning!
agree
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
