Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.1) with ESMTP id KAA03077 for ; Tue, 27 Apr 1999 10:31:42 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA08383; Tue, 27 Apr 1999 10:31:01 -0400 (EDT) To: Christophe Labouisse cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Strange behavior In-reply-to: Your message of 27 Apr 1999 08:03:03 +0200 Date: Tue, 27 Apr 1999 10:31:01 -0400 Message-ID: <8381.925223461@sss.pgh.pa.us> From: Tom Lane Christophe Labouisse writes: >> There is a hack in the parser that tries to transform the first of these >> into this: >> >> select crit_url from crit where crit_url like 'films/%' >> AND crit_url >= 'films/' AND crit_url <= 'films/\377' >> order by crit_url; > Well I guess that's it since \377 in fr_FR is ÿ (ydierisis). And I suppose that sorts before, or the same as, plain y? Oops. As a temporary measure you could rebuild with USE_LOCALE turned on; the parser code is set up not to generate the <= clause if that's defined. But we need a better solution. regards, tom lane