I saw a question at a StackOverflow site:
http://dba.stackexchange.com/questions/151199/why-cant-rows-inserted-in-a-cte-be-updated
regarding statements with CTEs that mofify a table twice, with an insert
and then an update:
(post:)
On 2016-10-01 13:13, Pantelis Theodosiou wrote:
I answered that this is unpredictable behaviour but the docs state only the
update-update and update-delete cases explicitly and the general wording is
about 2 updates.
It's documented[1] behavior:
"All the statements are executed with the same
Yes, thank you. I missed mentioning that part. It is the undelying reason
of the behaviour.
But surely it wouldn't hurt to add the 2 cases (insert-update,
insert-delete) in the last paragraph. I mean the update-delete is also
explained by the same reason.
> Trying to update the same row twice in
On 2016-10-01 1:37 PM, Pantelis Theodosiou wrote:
Yes, thank you. I missed mentioning that part. It is the undelying reason
of the behaviour.
But surely it wouldn't hurt to add the 2 cases (insert-update,
insert-delete) in the last paragraph. I mean the update-delete is also
explained by the sam
Not entirely sure but seems wrong to me...
thanks,
Erik Rijkers
--- doc/src/sgml/parallel.sgml.orig 2016-10-01 19:45:57.315099655 +0200
+++ doc/src/sgml/parallel.sgml 2016-10-01 19:46:32.622854693 +0200
@@ -406,7 +406,7 @@
unsafe, because this would require predicting every operation whic