<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Peter Eisentraut wrote:
<blockquote cite="mid200608282146(dot)01122(dot)peter_e(at)gmx(dot)net" type="cite">
<pre wrap="">Naz Gassiep wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If the violation of the constraint really is being caused
WITHIN the query, doesn't that violate the principle of atomicity?
I.e., operations and entities should be considered a single entire
construct rather than a collection of smaller, discrete parts.
</pre>
</blockquote>
<pre wrap=""><!---->
The principle of atomicity merely says that transactions are either
performed entirely or not at all. If the transaction is not performed,
then there is no violation of atomicity.
</pre>
<blockquote type="cite">
<pre wrap="">conwatch=# UPDATE replies SET rgt = rgt + 2 WHERE postid = 18 AND rgt
</pre>
<blockquote type="cite">
<pre wrap="">= 11;
</pre>
</blockquote>
<pre wrap="">ERROR: duplicate key violates unique constraint "replies_rgt_postid"
</pre>
</blockquote>
<pre wrap=""><!---->
This is a well-known deficiency in PostgreSQL. You will have to work
around it somehow (by changing the query, the schema, or the index).
</pre>
</blockquote>
Do we have an ETA on fixing it? Or is it a long term outstanding issue
with no ETA as yet?<br>
Thanks for the reply,<br>
- Naz<br>
</body>
</html>