From: | Terry Lee Tucker <terry(at)chosen-ones(dot)org> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: question on trigger |
Date: | 2012-02-11 16:53:15 |
Message-ID: | 1654881.XedbOmu4no@genesis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Saturday, February 11, 2012 09:22:44 AM mgould(at)isstrucksoftware(dot)net
wrote:
> I will have several triggers which will make sure that the data in some
> columns in in uppercase format. For insert it is a no brainer, however for
> updates, it is better to check and see if the new values is the same and
> only update if different? We are not talking about a huge number of
> transactions. In one day we might have at the most 3000 transactions.
>
> Michael Gould
> Intermodal Software Solutions, LLC
> 904-226-0978
--
Michael:
I am by no means an expert on database performance; however, it seems to me
that you would waste more cycles checking if things changed than simply
forcing upper case for all to which this criteria applies. The whole record is
going to be written to the database anyway.
Terry Lee Tucker
Office: 336-372-6812
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitriy Igrishin | 2012-02-11 19:27:15 | Unambiguous identification of the cluster. |
Previous Message | Magnus Hagander | 2012-02-11 16:25:44 | Re: ERROR: operator does not exist: integer = character varying |