| From: | Jonathan Bartlett <johnnyb(at)eskimo(dot)com> |
|---|---|
| To: | Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp> |
| Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Locking rows |
| Date: | 2003-02-28 18:55:58 |
| Message-ID: | Pine.GSU.4.44.0302281054450.13762-100000@eskimo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> ordered. But while I gathering the data, which takes more than one
> query, a customer might come along and cancel an invoice.
So what? Wouldn't you have the same situation if they cancelled
imediately after you finished the report?
Jon
>
> In that case I would print a receipt for something that was cancelled.
>
> I need to find a way to avoid this. I thought locking was a way around
> this ... or maybe I need to change my "business" logic or the way the
> app gathers the data?
>
> Jc
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2003-02-28 19:01:34 | Re: postgres error reporting |
| Previous Message | Ed L. | 2003-02-28 18:20:27 | Re: 7.4? |