Am Donnerstag, 16. August 2007 15:21 schrieb bhyuan:
> Maybe SQL injection-like security issues will occour,
> but I find that differend version of Postgresql get different result.
That just shows that some versions are more broken than others. But there was
a lot of thought put into the current
On Wed, August 15, 2007 21:15, Phoenix Kiula wrote:
>
> Thanks. Here's my locale information:
>
>> locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en
Thanks for your replay.
Maybe SQL injection-like security issues will occour,
but I find that differend version of Postgresql get different result.
Such as the sql
set client_encoding='SJIS';
select '\xc3\xaa',* from xxx;
on V7.4 @RH3 got
\xc3\xaa
on [EMAIL PROTECTED] got
(blank)
on [EMA
Am Donnerstag, 16. August 2007 08:40 schrieb bhyuan:
> Can I ignore the error message by confiing the config file?
No, there are not provisions for that. Some errors of this type used to be
ignored, but that led to SQL injection-like security issues, so you don't
want that.
--
Peter Eisentrau
hi
I use UTF-8 as server character encoding,
and use sjis as client character encoding.
For some reason, some none sjis encoding character was insert into the database.
WHEN I use
set client_encoding='SJIS
select * from xxx
I got such error message
Native Error: ERROR: character 0xc2a0 of encoding
