Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g080QVB24745 for ; Mon, 7 Jan 2002 19:26:31 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g080QVg15337; Mon, 7 Jan 2002 19:26:31 -0500 (EST) To: "Albrecht Berger" cc: pgsql-sql@postgresql.org Subject: Re: SELECT * FROM xy WHERE name LIKE '%german special char' In-reply-to: <027901c197d2$562a65b0$677ba8c0@w2k> References: <027901c197d2$562a65b0$677ba8c0@w2k> Comments: In-reply-to "Albrecht Berger" message dated "Tue, 08 Jan 2002 00:23:37 +0100" Date: Mon, 07 Jan 2002 19:26:31 -0500 Message-ID: <15334.1010449591@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/47 X-Sequence-Number: 6138 "Albrecht Berger" writes: > The Statement > SELECT * FROM XYZ WHERE name LIKE '%Müller%' > doesn't any of a matching row. > Is there a solution for this problem ? LIKE '%M_ller%' doesn't work, too ! The only way I could see for the underscore not to match is if the character is actually stored as two or more bytes, but Postgres doesn't know it should treat that sequence as a single logical character. Are you using a multibyte character set representation (eg, Unicode)? If so, did you build Postgres with MULTIBYTE support enabled, and did you specify the correct character set when you created the database? If you're not sure about this theory, try looking to see whether length() of one of the problem strings agrees with the number of characters you think there are. regards, tom lane