PKEYS and Objects

[Alejandro Imass]

> primary keys to me seem prehsitoric. there are 2
> keys
> because one is specific for that table and the other
> is
> a reference for the data object.  And the whole
> system
> is not based on relational databse but object based
> approach with inheretence with persient data and
> objects.
>  

I understand this. BTW I'm trying to model 1 table per
Object storage. I mean, 1 tables holds all objects of
a class.

Also, could you take a look at this over-simplified
model for Inventory. I have not yet written the
explanation but there are some things I would like
someone to validate. For example I used aggregation
(part-of) for all things that are pertinent to an item
record. Even though there will be associations to
other objects of the same type.

In other words...

If you see in the model there can be many
item_suppliers. In this case it is aggregation because
item_supplier is part-of an item, but the suppliers
themselves are specializaed objects that come from
(derived from) the company address book (not-shown in
the model), and there should (will be) be an
association between the item_supplier class and the
supplier class.

Please I would appreciate many comments on this since
I'm trying my best to break my relational paradigm.
That's why I want to start Inventory very small with
the components, business objects (described in the
attached diagram), and tables, and have some working
little app by next week.


Also, could someone please tell me what tool(s) are
they using for docbook manipulation on GNU/Linux ?!
In the mean time I'm documenting with exmaples I've
found here and there. Also, if someone has (or knows
of) a DocBook tag reference (quick guide) I would
really appreciate it.



Saludos,
Alejandro

__________________________________________________
Do You Yahoo!?
Yahoo! Messenger - Talk while you surf!  It's FREE.
http://im.yahoo.com/

inv_classes-0.0.1
Description: inv_classes-0.0.1