From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBCCTS issues |
Date: | 2005-07-06 02:30:40 |
Message-ID: | 5FCCEEC4-FDF9-4299-8551-B2F9D11998B6@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 5-Jul-05, at 7:05 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>> Does anyone know what the spec says if a parameter is registered and
>> the underlying type is not the same as the registered type?
>>
>> for instance registerOutParameter( n, Types.Real ) where the
>> underlying
>> type is float8
>>
>> In general should we be attempting to convert to the case requested ?
>>
>
> Ok I stared at the spec a bit..
>
> It seems like the type you specify when registering is the type you
> intend to retrieve via a get...() method, and the spec seems to imply
> that the driver should cast the parameter to that type.. but it's
> vague
> as usual.
>
> The datatype conversion tables appendix does not talk about datatype
> conversion on CallableStatement.get...() at all (though it does talk
> about conversion in ResultSet).
>
> So I suppose we should probably accept it and do a cast to the
> appropriate type on return.
I don't think anyone will mind if we make it easier for them.
>
> Am I right in thinking that OUT parameter types aren't considered part
> of a function's signature and don't contribute to overloading at all?
At the moment that is true, yes
>
> -O
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Maik Wiege | 2005-07-06 19:19:18 | get row count from a "cursor resultset" |
Previous Message | Oliver Jowett | 2005-07-05 23:05:15 | Re: JDBCCTS issues |