| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | RE: Primary Key Update issue ? |
| Date: | 2019-09-06 09:34:08 |
| Message-ID: | VisenaEmail.10.c4ad345de4e82645.16d05ebdf78@tc7-visena |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
På fredag 06. september 2019 kl. 11:25:36, skrev Patrick FICHE <
Patrick(dot)Fiche(at)aqsacom(dot)com <mailto:Patrick(dot)Fiche(at)aqsacom(dot)com>>:
Hi Andreas,
Thanks a lot for your answer, which solves this case.
I was still a bit surprised as this is linked to transaction management while
I have here a single statement until I saw the Compatibility Remark in
documentation :Also, PostgreSQL checks non-deferrable uniqueness constraints
immediately, not at end of statement as the standard would suggest.
FWIW - PostgreSQL behaves like Oracle in this regard. -- Andreas Joseph Krogh
CTO / Partner - Visena AS Mobile: +47 909 56 963 andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com> www.visena.com <https://www.visena.com>
<https://www.visena.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnaud L. | 2019-09-06 10:26:03 | Bad estimates on GIN bigint[] index |
| Previous Message | Patrick FICHE | 2019-09-06 09:25:36 | RE: Primary Key Update issue ? |