From: | Florian Weimer <fweimer(at)bfk(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Damiano Bolzoni <damiano(dot)bolzoni(at)gmail(dot)com>, Sylvain Leroux <sl20(at)wanadoo(dot)fr>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Search content within a bytea field |
Date: | 2009-09-03 13:59:11 |
Message-ID: | 82iqg0w2mo.fsf@mid.bfk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
* Tom Lane:
> The JDBC environment behaves differently because setString and so on
> do not produce unmarked literals --- there's an implicit cast to
> some datatype. So you have to make sure you've picked a
> parameter-setting function that is reasonably compatible with the
> intended operation.
You can append "?stringtype=unspecified" to the JDBC URL, and you get
bevahior which matches more closely what other (non-Java) interfaces
do.
> This is a good thing, really; it tends to keep the system from
> choosing an unexpected operation.
It more or less prevents use of fancy types. There doesn't seem to be
to set an unspecified type on a per-parameter basis, unfortunately.
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2009-09-03 17:12:25 | Re: Search content within a bytea field |
Previous Message | JUNG, Christian | 2009-09-03 10:47:56 | Re: PATCH: SET ROLE as connection parameter |