Not sure if this is the right group but I've come across a problem I'm at a
loss to model properly. Here's the setup:
A model contains three entities ("Level"s) describing projects:
- Project Family records, each referencing several

When time comes to build transactional databases (as opposed to data
wharehouses), I belong to the school that STRONGLY believe in
normalizing data with high integrity mechanisms.  I know all the
performance cons but IMHO, pros largely overwhelme.

I would appreciate your advice about the design of the following
schema:
We have a database of products and we know that:
- a product is of a certain type

Uh, I've been away for the weekend but some new questions about
normalization non the less popped up ( it seems every time I give a
thought about the subject, a new question arises ). I hope you don't
mind if I ask some more, cause there's no way I can figure out this

I am looking for people who have an interest in object oriented
databases, primarily to share ideas or to find out end-user
requirements.
I am currently working on an object oriented database product, which

1) For DB to be in 1NF there must be no multi-valued attributes, and
no repeating groups. When so, data is said to be atomic. One site
claims that even first name and last name must be featured in separate
columns, but some other sites did  put  both first name and last name