This locale-thing sounds good...:-)
As I remember, we've changed the locale settings after the creation of the
table.
The former opinions (space after the text, value length, etc.) didn't help us
too much.
Anyway, thanks to all.
So, I try to re-create the index.
Attila
Quoting Tom Lane <[EMAIL
Attila Kevei <[EMAIL PROTECTED]> writes:
> Our database has a SELECT problem using varchar columns in WHERE clause
> (but not in all rows!!!).
> We can fix the whole table (or just the row) as shown below but later it
> seems wrong again (and after the fix the row isn't UPDATEd).
Very bizarre.
Attila Kevei writes:
> goodwill=>select * from users where user_login='test';
> user_id|user_login|user_passwd|user_exp
> ---+--+---+
> (0 rows)
>
> goodwill=> select * from users where user_id=4;
> user_id|user_login|user_passwd |user_exp
> ---+--+---
- Original Message -
From: "Attila Kevei" <[EMAIL PROTECTED]>
> goodwill=>\d users
> Table= users
>
+--+--+-
--+
> | Field | Type|
Length|
>
+--
A space or something like that is also what I was thinking of.
I'd suggest to:
select * from users, length(user_login) where user_id=4;
before and after the update.
V.Paul
No, there's no space.
The query (point 4. below) after the fix (point 3.) is the _same_ as the first
(p.1.).
In the first select there's no result but in the last select we get the right
result.
Attila
Quoting [EMAIL PROTECTED]:
1.
> > goodwill=>select * from users where user_login='test';
> >
Attila Kevei wrote:
> Hi,
>
> Our database has a SELECT problem using varchar columns in WHERE clause
> (but not in all rows!!!).
> We can fix the whole table (or just the row) as shown below but later it
> seems wrong again (and after the fix the row isn't UPDATEd).
>
> Any idea?
>
> Thanks
>
