| From: | "Angva" <angvaw(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: multi-row check constraints? |
| Date: | 2007-03-27 21:38:07 |
| Message-ID: | 1175031487.415083.198310@l77g2000hsb.googlegroups.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sorry for the late reply, but thanks for your input, Jeff and Greg.
Greg, the trigger percent_two works for each statement. Would it be
possible to defer any check until the end of the transaction? For
example, I may need to insert into hundred values(1,25), followed by
(1,75), without the 25 immediately bombing.
Also is this solution safe for concurrent DML? I recently read an
Oracle solution to a similar problem in this blog entry's comments -
http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html
- and they said you need to lock before and after the validation.
Thanks,
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Angva | 2007-03-27 22:10:39 | Re: multi-row check constraints? |
| Previous Message | Chris Browne | 2007-03-27 21:34:28 | Re: Is there a shortage of postgresql skilled ops people |