Re: BUG #3493: Cannot find data with = operator - Mailing list pgsql-bugs

From Douglas Toltzman
Subject Re: BUG #3493: Cannot find data with = operator
Date
Msg-id 0292D49F-C248-49A9-AF81-1A9CCAC61DFA@oakstreetsoftware.com
Whole thread Raw
In response to Re: BUG #3493: Cannot find data with = operator  (Michał Niklas <michal.niklas@heuthes.pl>)
List pgsql-bugs
The schema specification you provided doesn't even include the column=20=20
"name", which you are selecting in your original message.  What is=20=20
the field type of "name" ?

On Jul 27, 2007, at 6:55 AM, Micha=C5=82 Niklas wrote:

> Alvaro Herrera wrote:
>> Michal Niklas wrote:
>>
>>
>>> isof_customer=3D# insert into customers (name) values ('KIOSK ');
>>> INSERT 437819002 1
>>> isof_customer=3D# select id,name from customers where name=3D'KIOSK ';
>>>  id | name
>>> ---------------+------------------
>>> (0 rows)
>>>
>>> isof_customer=3D# select id,name from customers where name like=20=20
>>> 'KIOSK ';
>>>  id | name
>>> ---------------+------------------
>>>         218856 | KIOSK
>>> (1 row)
>>>
>>
>> What's the type of the name column?  Please be specific.
>>
>
>
> It is varchar.
>
> I'm sorry I didn't reported data structure.  This table has many=20=20
> columns and indexes,
> and there is fragment of sql to create this table:
>
> create table "customers" (
>  "id" serial,
>  "customer" varchar(254) default '',
>  -- other columns
>  Constraint "customers_pkey" Primary Key ("id")
> );
>
> create index customer_idx on customers (customer);
> -- other indexes
>
> --=20
> Regards,
> Michal Niklas
> Poland
>
>
> ---------------------------(end of=20=20
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that=20=20
> your
>       message can get through to the mailing list cleanly

Douglas Toltzman
doug@oakstreetsoftware.com
(910) 526-5938

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #3494: may be Query Error: subplan does not executed
Next
From: Tom Lane
Date:
Subject: Re: BUG #3494: may be Query Error: subplan does not executed