Re: Help! Difficulty understanding DB -> Object mapping
- From: "frebe" <fredrik_bertilsson@xxxxxxxxxxx>
- Date: 8 May 2005 23:39:34 -0700
> I see your point here, but orders may be volatile - you may want to
> change a description or some other data per customer per order -
maybe a
> customized version of a product.
Yes, if you are producing customized products, this is probably a good
design.
> Also, if you basically move everything to ProductVersion, you might
as
> well consolidate the versions into one table, no?
> PRODUCT: Product_ID, Product_Version, Title, Price
> ORDER_ITEM: Order_ID, Product_ID, Product_Version
I would still have a product table with only Product_ID as primary key.
There might be information for which you don't need to track history
changes. And a customer selects a product, he/she selects a Product_ID.
The customer can not select version. He/she will always get the latest
version.
Fredrik Bertilsson
http://butler.sourceforge.net
.
- References:
- Help! Difficulty understanding DB -> Object mapping
- From: usenet . news . account
- Re: Help! Difficulty understanding DB -> Object mapping
- From: frebe
- Re: Help! Difficulty understanding DB -> Object mapping
- From: usenet . news . account
- Re: Help! Difficulty understanding DB -> Object mapping
- From: frebe
- Re: Help! Difficulty understanding DB -> Object mapping
- From: Mike Austin
- Help! Difficulty understanding DB -> Object mapping
- Prev by Date: Re: Lahman, how ya doing?
- Next by Date: Re: Rose & Code generation in C++
- Previous by thread: Re: Help! Difficulty understanding DB -> Object mapping
- Next by thread: Re: Help! Difficulty understanding DB -> Object mapping
- Index(es):
Relevant Pages
|