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 more
sincethe 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 not
sure(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. :(
--
Jim C. Nasby, Data Architect jim@nasby.net
512.569.9461 (cell) http://jim.nasby.net
