| From: | Aditya <aditya(at)grot(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | sfpug(at)postgresql(dot)org |
| Subject: | Re: reservation overlap constraint checking? |
| Date: | 2005-05-20 19:03:48 |
| Message-ID: | 20050520190348.GB90547@mighty.grot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
Josh,
On Fri, May 20, 2005 at 11:29:11AM -0700, Josh Berkus wrote:
> Aditya,
>
> > however, that seems less than elegant because there is time between the
> > check and the insert for a competing entry to get inserted....so next thing
> > to try is a constratint:
>
> Use a transaction and "select for update".
Sorry, I'm unclear on how this would help since I'm worried about an
intervening insert rather than an update. Am I missing something?
Thanks,
Adi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya | 2005-05-20 19:44:32 | Re: reservation overlap constraint checking? |
| Previous Message | Josh Berkus | 2005-05-20 18:29:11 | Re: reservation overlap constraint checking? |