Re: Strange inconsistency with UPDATE

From: "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com>
To: "Michael Glaesemann" <grzm(at)seespotcode(dot)net>
Cc: "Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Strange inconsistency with UPDATE
Date: 2007-08-17 04:17:33
Message-ID: e373d31e0708162117r7bf24e22p69f6cf68a0f66366@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I suspect you're not showing us the exact queries you're running. For
> one, you can't have a table named TABLE (without quotes) in PostgreSQL.

Of course. The data is a tad private, hence the simple table and
column names represented in uppercase.

> Perhaps something else you changed when changing the table name,
> maybe to simplify the appearance of the query, affects the results
> you're seeing. Things appear to work as expected on my end.

Except for the name of the table and the column, everything is exactly
the same as the queries I'm running. I just pasted those things into a
text editor and find-replaced mytable to "TABLE" and mycolumn to
"COLUMN". (Note: mytable and mycolumn are also aliases for posting to
a public forum).

The problem remains. The other tip -- to loop through each record and
update it -- is precisely what I was trying to escape with a simple
SQL query that seems fairly standard.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Phoenix Kiula 2007-08-17 04:26:45 Re: Strange inconsistency with UPDATE
Previous Message Tom Lane 2007-08-17 04:14:29 Re: SELECT ... FOR UPDATE performance costs? alternatives?