X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 964B49FAC9B for ; Tue, 25 Jul 2006 08:00:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 52519-01-2 for ; Tue, 25 Jul 2006 11:00:29 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by postgresql.org (Postfix) with ESMTP id A1B829FB293 for ; Tue, 25 Jul 2006 07:27:06 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id m3so2613698ugc for ; Tue, 25 Jul 2006 03:27:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=bitGIsOZEux/j/6Zezo3SA17IXqQ+MTjurfs4WdlQ0PAX9K6H4xfTWv7op+UGeB4DePCKBQupcrhW6nQxM0eUCWK3NA3kIiN1r9GuZvm+/KIp9HMNE8CHi/STpxG3/hd3S+nFejwDZncSz/AWWqZy5Xy0Y9qRBRyykX9r0lOq8Y= Received: by 10.66.219.11 with SMTP id r11mr4526784ugg; Tue, 25 Jul 2006 03:27:01 -0700 (PDT) Received: by 10.66.241.4 with HTTP; Tue, 25 Jul 2006 03:27:01 -0700 (PDT) Message-ID: <1c66bda80607250327k445186cesa5e36430929a4a22@mail.gmail.com> Date: Tue, 25 Jul 2006 22:27:01 +1200 From: adey To: "Peter Eisentraut" Subject: Re: UTF8 characters Cc: pgsql-admin@postgresql.org, "PostgreSQL Admin" In-Reply-To: <200607211842.14935.peter_e@gmx.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_247586_8143261.1153823221680" References: <20060714154218.10234.qmail@web55703.mail.re3.yahoo.com> <44B7C17E.7080901@andycc.net> <44C0FB2D.4040605@productivitymedia.com> <200607211842.14935.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.696 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, HTML_40_50, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/201 X-Sequence-Number: 22447 ------=_Part_247586_8143261.1153823221680 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I had the same problem when upgrading v7.4 database to v8, SQL-ASCII to UTF8 - we had to replace single backslashes with double backslashes in the v7 database to get the data to display correctly, then dump and restore in v8 / UTF8. Have we done something wrong please? On 7/22/06, Peter Eisentraut wrote: > > PostgreSQL Admin wrote: > > I had my database set to SQL_ASCII and switched to UTF8, but now I > > notice that I must add a slash for periods/dots ( \. vs . ) to insert > > into varchar. Is this normal? > > No. > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > ------=_Part_247586_8143261.1153823221680 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I had the same problem when upgrading v7.4 database to v8, SQL-ASCII to UTF8 - we had to replace single backslashes with double backslashes in the v7 database to get the data to display correctly, then dump and restore in v8 / UTF8. Have we done something wrong please?

On 7/22/06, Peter Eisentraut <peter_e@gmx.net> wrote:
PostgreSQL Admin wrote:
> I had my database set to SQL_ASCII and switched to UTF8, but now I
> notice that I must add a slash for periods/dots ( \. vs . ) to insert
> into varchar.   Is this normal?

No.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

              http://archives.postgresql.org

------=_Part_247586_8143261.1153823221680--