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!
---(en
> 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
* "Qty")
> END
>, "UserID"
> FROM "Transaction" NATURAL JOIN "TransactionItem";
>
> As far as speed, speed is always an issue. PostgreSQL is going to
> perform better than Access, but don't use good performance as a crutch
> fo
le to take it too far. There is a
time when de-normalizing a database will significantly improve its
performance even if it involves duplicating data. 4NF is not the goal
of DB design, having a usable database is. Knowing when and how to
de-normalize is much more difficult than learning to
do some index tuning.
>
> --
> Brandon Aiken
> CS/IT Systems Engineer
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Wednesday, September 06, 2006 2:05 PM
> To: pgsql-general@postgresql.org
&
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 ready
To: pgsql-general@postgresql.org
Cc:
Subject: [GENERAL] Database design and triggers...
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 i
the
queries are slow, do some index tuning.
--
Brandon Aiken
CS/IT Systems Engineer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 06, 2006 2:05 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Database desi
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 s
