| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "alexandre :: aldeia digital" <alepaes(at)aldeiadigital(dot)com(dot)br> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Outer Join with For Update |
| Date: | 2002-09-03 21:31:19 |
| Message-ID: | 18071.1031088679@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"alexandre :: aldeia digital" <alepaes(at)aldeiadigital(dot)com(dot)br> writes:
> SELECT A.id, B.desc from A left join B ON B.id=A.id FOR UPDATE OF A,B
> If I have a null rellation in B, the error in postgres is:
> "SELECT FOR UPDATE cannot be applied to the nullable side of an OUTER JOIN"
Yup.
> DB2 simply ignore the FOR UPDATE ...
> I think that is the correct form...
That seems obviously wrong to me. What good is a FOR UPDATE if it fails
to lock down the rows that created your result?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mallah | 2002-09-03 21:59:54 | Re: tree structures in sql - my point of view (with request |
| Previous Message | Peter Eisentraut | 2002-09-03 18:55:52 | Re: Update Help |