From: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: pgsql-sql@postgresql.org
Subject: Constraint doesn't see a currently insertet record
Date: Fri, 11 Feb 2005 19:10:50 +0100
Message-ID: <ED4E30DD9C43D5118DFB00508BBBA76EB165BE@neptun.sonorys.at> (raw)
Hi,
yes that's my problem.
I've got a table and I put lots of contraints on it so that data stays
consistent. One constraint calls a fcn to do some kind of count() over that
table but it omits the 'to be inserted record'. What to do?
concrete problem:
Suppose a table
i | tel | status | ...
..| \d+ | 1-7 | ...
status can be active, deleted or some more values
There may be not two rows where tel is equal and status is not deleted.
Other: As long as status=deleted there may be duplicate tel columns.
How would I make that sure?
My try was to create a check constraint like
("status" = 7) OR (("status" <> 7) AND (num_of_equal_tel_status_not_7("tel")
<= 1))
where num_of_equal_tel_status_not_7 is:
SELECT count(*) FROM "this table" WHERE "tel"=$1 AND "status"<>7
Note: status=7 means deleted
This works well until two recoreds are inserted which are status<>7.
The second gets inserted because the new record is not yet visible.
Another Idea was to make a trigger. But BTW how do I access a trigger
parameter if my trigger function must not have any parameter??????????
Ideas?
Tahks for any
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: robert.koepferl@sonorys.at
Subject: Re: Constraint doesn't see a currently insertet record
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB165BE@neptun.sonorys.at>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB165BE@neptun.sonorys.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox