> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Note that EUC_TW or any multibyte encodings that are allowed for
> > backend side, do not contain such ASCII special characters as "|" and
> > should be safe for the parser and the regexp routines.
>
> But the point is that a pg_wchar is being squeez
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Note that EUC_TW or any multibyte encodings that are allowed for
> backend side, do not contain such ASCII special characters as "|" and
> should be safe for the parser and the regexp routines.
But the point is that a pg_wchar is being squeezed down to a
> "pierre" <[EMAIL PROTECTED]> writes:
> > I make postgres 7.1.3 version in my linux system with --enable-multibyt=
> > e=3DEUC_TW, but=20
>
> > I got some problem when I exec sql command below, in chinese character=
> > (CName ~* '=A6|'') the chicode is 0xA67C -> 0x7c is ascii '|" ,
"pierre" <[EMAIL PROTECTED]> writes:
> I make postgres 7.1.3 version in my linux system with --enable-multibyt=
> e=3DEUC_TW, but=20
> I got some problem when I exec sql command below, in chinese character=
> (CName ~* '=A6|'') the chicode is 0xA67C -> 0x7c is ascii '|" , I guess =
>
