Re: Update Query doesn't affect all records - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Update Query doesn't affect all records
Date
Msg-id dcc563d10908051027g11b213dbkdfdc85fe0b74fea@mail.gmail.com
Whole thread Raw
In response to Re: Update Query doesn't affect all records  (Csaba Nagy <nagy@ecircle-ag.com>)
Responses Re: Update Query doesn't affect all records  (Sam Mason <sam@samason.me.uk>)
Re: Update Query doesn't affect all records  (Alban Hertroys <dalroi@solfertje.student.utwente.nl>)
List pgsql-general
On Wed, Aug 5, 2009 at 6:56 AM, Csaba Nagy<nagy@ecircle-ag.com> wrote:
> Hi Andor,
>
> On Wed, 2009-08-05 at 14:15 +0200, Schindler Andor wrote:
>> Can anyone tell me, how this is possible? If we insert 12 on the end, then
>> it decreases, but 11 remains the same. The problem only occurs, when the
>> where condition contains "sorrend > 9" or less.
>
> I bet the "sorrend" column is of some text type, and the "sorrend > 9"
> comparison is a text comparison. Try "sorrend::integer > 9" and it
> should work ;-)

That's kinda what I was thinking at first, but the pastebin he posted
showed them in proper int type order.  So I'm not sure why it's doing
what it's doing.  I'd ask Schinlder if he could post a completely self
contained example of the problem, including the create table and
insert statements used to create the test set.  Otherwise we're blind
men describing an elephant.

pgsql-general by date:

Previous
From: Michael Gould
Date:
Subject: LDAP using Active Directory
Next
From: Sam Mason
Date:
Subject: Re: Update Query doesn't affect all records