Hello Again,
Yes, you're right. What I am talking about is a material view. Since
I'm not sure yet which would be best (Material View Vs. Normal View) I
will first try a normal view and if it turns out to be too slow I can
always switch to a Material View.
Thanks!
Hi Brandon,
Thank you for your response.
Yes, I see what you mean when you say that I can list Qty in signed
integers and use a view. Good point.
But I'm not sure as to using a view vs using a permanent table updated
by triggers. It seems we are dealing with the clasic tradeoff between
speed
It just occurred to me. The purpose of normalizing the information and
having it stored on two separate tables is defeated if I have another
table that contains the same information but in an un-normalized
fashion. I would end up with two copies of the same information, one
normalized but not
Hi Brandon, thanks for answering.
The information regarding a transaction is stored on two separate
tables due to normalization. The first table stores general information
regarding the transaction like Transaction number, date, customer ID,
type of transaction, userID etc... The second table
Hi everybody. Hope I'm posting in the correct group.
My question is part design and part implementation.
Since we are creating an inventory system we need to have the clients
pull up current inventory. Also, we need to have the past transactions
stored for reference and billing. In our previous
