Skip site navigation (1) Skip section navigation (2)

Re: postgresql v7.1.3 bug report

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "pierre" <cti848(at)www(dot)textilenet(dot)org(dot)tw>
Cc: pgsql-bugs(at)postgresql(dot)org, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Subject: Re: postgresql v7.1.3 bug report
Date: 2001-09-04 15:54:55
Message-ID: 26684.999618895@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"pierre" <cti848(at)www(dot)textilenet(dot)org(dot)tw> 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 =
> you system reject '|' this byte, but it was Big5 Code 2nd byte , How can I =
> avoid this proble??

> SELECT * FROM ifabinstn Where((CName ~* '=A6|') OR FALSE) ORDER BY CName

> Warning: PostgreSQL query failed: ERROR: Invalid regular expression: empty =
> expression or subexpression in DB/pgsql.php on line 163
> ERROR: Invalid regular expression: empty expression or subexpression=20


I am thinking that p_ere's local "char c" (regcomp.c, about line 304 in
current sources) should have been declared "pg_wchar c".  Tatsuo, what
do you think?  Are there any other places in this file where char should
be pg_wchar?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tomasz ZielonkaDate: 2001-09-04 22:26:31
Subject: Re: Error in backend/storage/lmgr/proc.c: ProcSleep()
Previous:From: guardDate: 2001-09-04 15:21:33
Subject: postgresql7.1x in cygwin

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group