Re: Identical command-line command will not work with \i metacommand and filename - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Identical command-line command will not work with \i metacommand and filename
Date
Msg-id 201004250101.o3P11dr22284@momjian.us
Whole thread Raw
In response to Re: Identical command-line command will not work with \i metacommand and filename  (John Gage <jsmgage@numericable.fr>)
List pgsql-general
John Gage wrote:
> > http://en.wikipedia.org/wiki/Byte_order_mark
> >
> > Tends to get added if you go through a Windows system. Useless for
> > utf-8 afaik. Confuse the hell out of you because various tools parse
> > and hide them then you pipe the file to a script and everything
> > falls over.
> >
> > Bunch of scripts available here to remove them:
> >  http://www.xs4all.nl/~mechiel/projects/bomstrip/
>
> Correct.  I found the following via Google.
> "I created a file utf8.rb with this content: C:\>ruby -e "p
> File.read('utf8.rb')" "\357\273\277puts \"Hello World\""
> The "\357\273\277" part is the Byte Order Mark for UTF-8, my editor
> automatically put it at the beginning of the file, because I saved it
> as UTF-8."
> At least it isn't some evil virus.  Have to do Mr. WorkAround now.

FYI, this is fixed in Postgres 9.0:

     Ignore leading UTF-8-encoded Unicode byte-order marker in
     psql (Itagaki Takahiro)

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Help me stop postgres from crashing.
Next
From: Andre Lopes
Date:
Subject: Problem compiling function with BEGIN WORK; COMMIT WORK;