| From: | Shianmiin <Shianmiin(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Another unexpected behaviour |
| Date: | 2011-07-19 15:44:22 |
| Message-ID: | 1311090262217-4612763.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Shianmiin wrote:
>
> I thought the Atomic should be at statement level, could anyone tell me
> why PostgreSQL behaves differently?
>
re-state for clarification purpose.
Since SQL is a set language, there is no concept of row order. I thought the
checking should be on a per set operation (i.e. per statement), not per
micro operation basis (e.g. in this case, the order of operations could
result in success/failure). I don't know how strict the standard defines
here and it could be implementation specific. Still wondering why PostgreSQL
does it differently from other major DBMS?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Another-unexpected-behaviour-tp4610242p4612763.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2011-07-19 16:37:10 | Re: Programmer ( Postgres), Milwaukee - offsite-Remote - onsite |
| Previous Message | Martin Gainty | 2011-07-19 15:27:15 | Re: Programmer ( Postgres), Milwaukee - offsite-Remote - onsite |