From: | "Dmitry Teslenko" <dteslenko(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Right way to reject INSERTs and UPDATEs |
Date: | 2008-07-29 10:25:21 |
Message-ID: | 91325fec0807290325h6bb80eb0g75f583d666fbe5d5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello!
I have postgresql table that stores dome date range: it has range-begin
and range-end columns of type date. I want to enforce that 1) range-begin
would always before range-end and 2) there would be no range overlaps.
First problem could be solved with CHECK constraint. The only possibility
to solve second problem is to use a trigger. Trigger would fire
BEFORE INSERT OR UPDATE and FOR EACH ROW and invoke pgplsql function
that returns NULL or "new" depending on condition met or not;
These solution work and enforce data integrity as needed. Sadly, database
interface I use (Trolltech Qt 3) can't track when trigger aborts
update or insert. Can I raise exception in trigger or something?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2008-07-29 10:33:03 | Re: Right way to reject INSERTs and UPDATEs |
Previous Message | valgog | 2008-07-29 10:08:01 | Re: array_accum() and quoted content |