| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Jean-Pierre Pelletier <pelletier_32(at)sympatico(dot)ca> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: setObject on PGInterval throws "Unknown Type null" |
| Date: | 2005-01-25 23:10:51 |
| Message-ID: | Pine.BSO.4.56.0501251803010.23282@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 25 Jan 2005, Jean-Pierre Pelletier wrote:
> "func(?)" will be rejected by the server at runtime if there is ambiguity,
Not always, sometimes it will resolve the ambiguity itself in a less than
expected manner:
http://archives.postgresql.org/pgsql-jdbc/2004-10/msg00114.php
> In the case of "? IS NULL", I don't understand how the type of the null
> would affect the evaluation of this boolean expression.
>
http://archives.postgresql.org/pgsql-jdbc/2004-10/msg00118.php
Oliver also mentions problems with anyelement/anyarray functions:
http://archives.postgresql.org/pgsql-jdbc/2004-10/msg00116.php
I am OK with all of these failings because they are easily solvable using
casts or strong typing, while the Types.OTHER case is not easily solvable.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-01-25 23:19:08 | Re: setObject on PGInterval throws "Unknown Type null" |
| Previous Message | Jean-Pierre Pelletier | 2005-01-25 22:58:15 | Re: setObject on PGInterval throws "Unknown Type null" |