Justin Muise <JMuise@esri.com> writes:
> Thank you for your quick response! Please see the attached image.
Hm. If I'm reading that correctly, you've got encoding set to UTF8
but the OS is going to think the encoding is WIN1252, which will likely
affect the behavior of isspace(), which'd successfully break this
function. I'm not sure how the system allowed you to do that.
I wonder though whether it wouldn't be better for SplitIdentifierString
to use scanner_isspace() rather than isspace(). That would cause it
to not treat things like as whitespace, but maybe that's OK.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
