From: | "Ken J(dot) Wright" <ken(at)ori-ind(dot)com> |
---|---|
To: | Byron Nikolaidis <byron(dot)nikolaidis(at)home(dot)com> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] problem with numeric |
Date: | 2000-02-02 05:51:17 |
Message-ID: | 3.0.32.20000201215115.0086ce80@ren.cncware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
At 20:52 02/01/2000 -0500, Byron Nikolaidis wrote:
>
>
>"Ken J. Wright" wrote:
>>
>> v6.5.3
>>
>> While testing the new ODBC driver I ran into the following problem with
>> queries on numeric fields. Unless the values are surrounded by single quote
>> marks, the query fails with the message: Unable to identify an operator '='
>> for types 'numeric' and 'float'. This occurs in the WHERE clause of the
>> query.
>>
>> SELECT * from tbl WHERE numfld = 99.125;
>> UPDATE tbl SET numfld = 99.13 WHERE numfld = 99.125;
>>
>> An INSERT works fine.
>>
>> These statements execute ok on float fields, but not numeric. This happens
>> via ODBC and also with psql from a Linux console.
>>
>> Ken
>>
>> ************
>
>Ok, I can put quotes around it, as long as you use a bound parameter.
>In other words, you have to use something like "select * from tbl where
>numfld = ?", and then bind parameter 1 to be the numeric type.
>
>The driver will not try to put quotes around a numeric embedded into an
>sql query.
>
>For completeness, I think Postgres should work with or without the
>quotes, after all, it is a numeric field. If this where the case, then
>flat queries (i.e., no Bounded parameters) would work too.
Yeah, I think the backend kinda goes for a Burton here. Like you say, it is
a numeric field!
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Jackson Ching | 2000-02-02 08:29:26 | Question on Cygwin-b20 |
Previous Message | Ken J. Wright | 2000-02-02 05:48:39 | Re: [INTERFACES] ODBC bind trouble with bigint |