Re: Prepared Statements: Inefficient Type Conversion? - Mailing list pgsql-jdbc

From James House
Subject Re: Prepared Statements: Inefficient Type Conversion?
Date
Msg-id 4623CCA0.305@part.net
Whole thread Raw
In response to Re: Prepared Statements: Inefficient Type Conversion?  (Kris Jurka <books@ejurka.com>)
Responses Re: Prepared Statements: Inefficient Type Conversion?  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc

Kris Jurka wrote:
>> It seems that using the prepared statement to pass the value as a
>> string causes all of the 40 million upid values in the table to
>> convert to string, rather than the string parameter being converted
>> to a number.   Can't the driver be smarter than that?
>
>
> You can try adding the url parameter stringtype=unspecified which will
> pass the String parameter untyped instead of as a String.
FWIW, that didn't seem to make a difference - actually, it takes even
longer to execute.

Thanks anyway.  We'll try to get the datatype of the column changed.



Attachment

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Bug in timezone-parsing?
Next
From: Kris Jurka
Date:
Subject: Re: Prepared Statements: Inefficient Type Conversion?