Postgres Pro
Downloads
Home   >   mailing lists

Re: Change server encoding after the fact - Mailing list pgsql-general

From Cody Caughlan
Subject Re: Change server encoding after the fact
Date
Msg-id CAPVp=gazwcHgFNLTpSv1AjKqxSyFgNbwGxor1ZQLzVAMBnX74Q@mail.gmail.com
Whole thread Raw
In response to Re: Change server encoding after the fact  (Scott Marlowe <scott.marlowe@gmail.com>)
Responses Re: Change server encoding after the fact  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general
Tree view
That worked, but "file" shows no difference:

$ iconv -f utf-8 -t utf-8 -c foo.sql > utf.sql
$ file -i foo.sql
foo.sql: text/plain; charset=us-ascii

$file -i utf.sql
utf.sql: text/plain; charset=us-ascii

So iconv didnt actually convert the file OR does is the "file" command just ignorant?

On Fri, Sep 30, 2011 at 12:41 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Fri, Sep 30, 2011 at 1:39 PM, Cody Caughlan <toolbag@gmail.com> wrote:
> Its a Rails app and I do have:
>   encoding: utf8


Hmmm, if you try this does it work (mostly)?

iconv -f utf-8 -t utf-8 -c < infile > outfile

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Change server encoding after the fact
Next
From: Dario Beraldi
Date:
Subject: Re: postgres for OLAP & data mining