I mean something else. You have a reference data set which is accessed
to get the current value of reference elements and store transactions to
record events. The transaction trails provide event history.
A price is in the reference data, its value transferred to a transaction
is no longer a price, it is a sale which represents the value of the
price at the time the event occurred.
How about reading your price data etc and just inserting a transaction
into your sales table? You do not need to update anything. You also
have integrity for multiple users.
T&B wrote:
Hi John,
A general rule of database design is to seperate reference and
transactional data. Then you can have a normalized database in a
dynamic environment.
Yes, I think that's what I am designing.
The reference data is the products table (and potentially customer
table etc)
The transactional data is the sale_products table which lists what
products went with each sale.
Or do you mean something else?
Thanks,
Tom
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
