| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Tjioe Ai Xin <xinxincute(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Can PostgreSQL do data type automated casting in |
| Date: | 2005-11-24 21:06:50 |
| Message-ID: | 6022BCB2-7A1B-47A2-AC85-CDBB7CBD127C@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
You're on fairly shaky ground using "allowed by the spec" as
justification. I'm thinking there are far more instances where people
expect Oid unspecified to work than
instances where they are going to change the type of the IN parameter
in the same statement.
Given that the default behaviour adheres to the spec, I'm not too
worried about the case below failing under these specific
circumstances. I presume it passes with the 8.0,8.1 behaviour.
Dave
On 24-Nov-05, at 3:47 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>> Looking at the test case is this a realistic situation ? Would
>> anyone really want to change the types of a parameter of a
>> statement ?
>
> It's allowed by the spec as far as I can tell, so we need to
> support it.
>
> -O
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-11-24 21:20:01 | Re: Can PostgreSQL do data type automated casting in |
| Previous Message | Oliver Jowett | 2005-11-24 20:50:03 | Re: Why is bool == java.sql.Types.BIT ?? |