| From: | Sylvain Leroux <sl20(at)wanadoo(dot)fr> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Search content within a bytea field |
| Date: | 2009-08-31 07:38:49 |
| Message-ID: | 4A9B7E09.1000300@wanadoo.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi,
And sorry for that:
Tom Lane a écrit :
> Sylvain Leroux <sl20(at)wanadoo(dot)fr> writes:
>> It seems to me that the problem is comming from the BYTEA type, not from
>> the prepared statement by itself: As far as I know the only operator
>> supported by BYTEA is concatenation. You can't even compare two BYTEA
>> for (in)equality - even less using the LIKE operator.
>
> Nonsense ...
But I was quite sure to have read that somewhere -- and indeed:
(in "PostgreSQL - second edition / ISBN:978-0-672-32756-8)
"PostgreSQL offers a single BYTEA operator: concatenation. [...]
Note that you can't compare two BYTEA values, even for
equality/inequality. You can of course convert a BYTEA value into
another value using CAST() operator, and that opens up other
operators."
I remember having found that annoying at the time - that's why I
remembered it. But it appears this statement was outdated -- or simple
false all along?
Anyway once again sorry for the misinformation.
Sylvain.
--
Website: http://www.chicoree.fr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dmp | 2009-08-31 13:39:19 | Re: Search content within a bytea field |
| Previous Message | Damiano Bolzoni | 2009-08-31 06:08:43 | Re: Search content within a bytea field |