| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Kris Jurka <books(at)ejurka(dot)com> |
| Subject: | Re: Can PostgreSQL do data type automated casting in |
| Date: | 2005-11-24 05:36:24 |
| Message-ID: | 43855158.7050100@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver Jowett wrote:
> I guess that we should tighten the checks in the query executor so that
> it will only consider types "compatible enough" if the new value is both
> of unspecified type *and* null?
With that change the test just fails differently:
ERROR: could not determine data type of parameter $1
since the test query ("SELECT ?") is actually one of the cases where
string-as-unspecified-type does not work.
I changed it to use a different query that still appears to exercise the
type-changing behaviour correctly ("SELECT CAST (? AS TEXT)") but
doesn't fail with a parameter of unspecified type.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-11-24 11:25:23 | Re: Room to optimize updates through ResultSet |
| Previous Message | Oliver Jowett | 2005-11-24 05:00:11 | Re: Can PostgreSQL do data type automated casting in |