On Sat, 2014-03-22 at 11:23 -0500, Jim Nasby wrote:
> On 3/21/14, 8:13 PM, David E. Wheeler wrote:
> > On Mar 21, 2014, at 2:16 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> >
> >> Surely if it were really a major annoyance, someone would have sent code to fix it during the last 4 years and
moresince the above.
> >>
> >> I suspect it's a minor annoyance :-)
> >>
> >> But by all means add it to the TODO list if it's not there already.
> >
> > I have cleaned up many a BOM added to files that made psql blow up. I think PGAdmin III was a culprit, though I’m
notsure (I don’t use, it, cleaned up after coworkers who do).
>
> Yes, my coworker that figured out what the problem was said the culprit here is actually pgAdmin. :(
Just a quick comment on this. Yes, pgAdmin always added a BOM in every
SQL files it wrote. That being said, since 2010, pgAdmin has an option
that allows the user to request the BOM writing (IOW, it's disabled by
default for new installations of pgAdmin). See in the
preferences/options window, "Query tool / Query file" sub-item, and
"Write BOM for UTF files" checkbox. Make sure it's unchecked.
Either your coworker has an older release (that would be older than 1.14
IIRC), or he didn't change the setting to make it work like he would
like.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
