From: | "Nat!" <nat(at)mulle-kybernetik(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #4574: LIKE fails on non-varying character with no wildcards |
Date: | 2008-12-09 14:07:03 |
Message-ID: | 200812091407.mB9E73A6011312@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 4574
Logged by: Nat!
Email address: nat(at)mulle-kybernetik(dot)com
PostgreSQL version: 8.3.5
Operating system: Mac OS X 10.4
Description: LIKE fails on non-varying character with no wildcards
Details:
The documentation claims:
http://www.postgresql.org/docs/8.3/interactive/functions-matching.html#FUNCT
IONS-LIKE
"If pattern does not contain percent signs or underscore, then the pattern
only represents the string itself; in that case LIKE acts like the equals
operator."
But:
create temporary table foo ( nummer character(12) );
insert into foo ( nummer) values( '1848' ) ;
select count(*) from foo where nummer = '1848' ;
-- returns 1
select count(*) from foo where nummer like '1848' ;
-- returns 0
drop table foo;
Whereas:
create temporary table bar ( nummer character varying );
insert into bar ( nummer) values( '1848' ) ;
select count(*) from bar where nummer = '1848' ;
-- returns 1
select count(*) from bar where nummer like '1848' ;
-- returns 1
drop table bar;
OTOH. Oracle has the same behaviour.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-12-09 14:50:00 | Re: BUG #4574: LIKE fails on non-varying character with no wildcards |
Previous Message | Tom Lane | 2008-12-09 13:10:15 | Re: BUG #4565: nextval not updated during wal replication, leading to pk violations |