[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] statement level triggers in PostgreSQL , anybody??
From:       Martijn van Oosterhout <kleptog () svana ! org>
Date:       2004-05-31 22:10:03
Message-ID: 20040531221003.GC436 () svana ! org
[Download RAW message or body]


This has nothing to do with triggers, it has to do with not being able
to defer UNIQUE constraints. The classic solution is:

update SET column = -column;
update SET column = -column+1;

The problem is that you're trying to update the primary key, which is a
bad idea is most situations.

On Thu, May 27, 2004 at 06:28:08AM -0700, rama wrote:
> Hi,
>      I am a bit troubled with the row-level triggers which PostgreSQL
> uses when using update table cpmmand.
>      For instance, if the primary key column has values 1,2,3,... and
> i want to update the whole column as column = colunm + 1 , then there
> is an error. This obviously works on databases such as mssql which has
> row level triggers.
>      Any suggestions so that i do not have to modify the query and
> still make it work in the postgresql database ??
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly

-- 
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]