On Mon, Sep 26, 2011 at 13:36, Itagaki Takahiro <itagaki.takah...@gmail.com> wrote: > On Mon, Sep 26, 2011 at 20:12, Magnus Hagander <mag...@hagander.net> wrote: >> I like it in general. But if we're looking at the BOM, shouldn't we >> also look and *reject* the file if it's a BOM for a non-UTF8 file? Say >> if the BOM claims it's UTF16? > > -1 because we're depending on manual configuration for now. > It would be reasonable if we had used automatic detection of > character encoding, but we don't. In addition, some crazy > encoding might use BOM codes as a valid character.
Does such an encoding really exist? And the code only executes when the user thinks he's in UTF8, right? So it would still only happen if the incorrect encoding was specified.. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
