From: | Antoine Reid <antoiner(at)hansonpublications(dot)com> |
---|---|
To: | "Madel, Kurt" <KMadel(at)USInspect(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Use a rule or a transaction |
Date: | 2000-08-15 18:43:14 |
Message-ID: | 20000815144314.A21306@wumpus.lan.edmarketing.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, Aug 15, 2000 at 01:57:17PM -0400, Madel, Kurt wrote:
> Hello,
>
> I am creating a web based (using php) class registration database with three
> tables directly effected by the registration process:
[snip]
> My question is, would it be better (faster) to use rules or to use a
> transaction.
How about using triggers? I have used pl/pgsql triggers in the past to do
similar things. I was not checking a maximum but definitely was keeping a
reference count. What you want is a trigger that increments on insert,
decrement on delete, and on update, IF the id changed, decrement the old
one, increment the new one.. I suspect you could also have another trigger,
on update on class, that would abort the transaction if class.size ever
becomes bigger than maxsize..
I can't really comment on performance though.....
> Is there a faster way to do this with rules or a better way to do it
> otherwise.
>
> TIF,
> Kurt
Hope it helps
Antoine
--
o Antoine Reid o> Alcohol and calculus <o>
<|> antoiner(at)hansonpublications(dot)com <| don't mix. Never drink |
>\ antoiner(at)edmarketing(dot)com >\ and derive. /<
From | Date | Subject | |
---|---|---|---|
Next Message | Qiron Adhikary | 2000-08-15 18:47:57 | Re: Copwatch database |
Previous Message | Thomas Swan | 2000-08-15 18:28:29 | Re: Functions with Null Arguments? |