From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "radoslav hodnicak" <rh(at)4096(dot)sk> |
Cc: | pgsql-bugs(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: BUG #3438: Problem selecting backslash from a byte array |
Date: | 2007-07-11 16:28:47 |
Message-ID: | 162867790707110928m25a13663i78662c00bd6a2d03@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
it's not bug. You didn't use any wild char. And like predicate isn't
defined for bytea. There is another strange behave
postgres=# select position(E'\\134\\134'::bytea in test) from backslashtest ;
position
----------
0
(1 row)
Regards
Pavel Stehule
>
> I create a table with a byte array column and insert a row with the byte 92
> into it (which is backslash). Then I want to select the row.
>
> Steps to reproduce:
>
> create table backslashtest (test bytea null);
>
> insert into backslashtest values (E'\\134'::bytea);
>
> select * from backslashtest where test like E'\\134'::bytea;
>
> Result:
> select returns no rows
>
> Expected result:
> select should return the row I've inserted
>
> Other remarks:
> select * from backslashtest where test like E'\\134\\134'::bytea;
>
> does what I expected from the original select, but that's wrong because I
> don't want two backslashes, only one
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-11 17:05:30 | Re: BUG #3438: Problem selecting backslash from a byte array |
Previous Message | radoslav hodnicak | 2007-07-11 15:57:51 | BUG #3438: Problem selecting backslash from a byte array |