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 [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
