Re: Inconsistent casting with literal vs parameter

Right, I missed that.

My last 2 cents on the whole topic. There is a fundamental design issue
here with deciding to handle the expression /column <
(value/literal/parameter typed or not)/ by converting the column to a
string. Obviously, with INSERT INTO the data values must be coerced to
the destination column type. In this case, while there is a
parsing/optimizing decision to be made, it should be made with a strong
bias to convert to the column type (and then handling any tricky
coercion failures or optimization issues).

Again thanks for your help,
Matt

Kris Jurka wrote:

>
>
> On Tue, 7 Feb 2006, Matthew Bellew wrote:
>
>> JDBC Driver Version: PostgreSQL 8.1 JDBC3 with SSL (build 404)
>>
>> So, does this mean this parameter is not properly respected in the
>> driver?
>>
>
> Yes, this parameter is only available in the 8.2 driver.
>
> Kris Jurka
>