Re: Table Design

Ciari,

> time on CD. However, we couldn't(or shouldn't?) capture that on one table.
> Would it be better to define a table for each type?
> Appreciate any professional help. Already have homemade Prozac.

as often there's not one solution that's good in any case .. but each solutions will be good in some query situations and might be bad in others. Have a look at
http://www.objectarchitects.de/ObjectArchitects/orpatterns/index.htm the stuff on mapping objects to tables and there the three ways to deal with inheritance and don't forget to look at the forces there.. They will provide you with a systematic apporoach to solve your problem ...

You may also have a look at the tutorial on flexible insurance systems at  http://www.objectarchitects.de/ObjectArchitects/papers/Presentations/index.htm The slides on reflective policy systems contain a few ideas on variable table schemes that might help ...
 http://www.objectarchitects.de/ObjectArchitects/papers/Presentations/ZippedPapers/STJA%20Tutorial%2099%20-%20Reflection.zip

Hope that's ProZac enough and you feel like some Viagra after that :-)

Cheers

Wolfgang

--
================================================================
EMail: wk_at_objectarchitects.de
Web:   http://www.objectarchitects.de/ObjectArchitects/