pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PLPGSQL with Multibyte Issue
4+ messages / 2 participants
[nested] [flat]

* PLPGSQL with Multibyte Issue
@ 2003-03-18 07:24  Frankie Lam <frankie@ucr.com.hk>
  0 siblings, 2 replies; 4+ messages in thread

From: Frankie Lam @ 2003-03-18 07:24 UTC (permalink / raw)
  To: pgsql-sql

Hi all,

I'm experiencing some problem with using multibyte character issues in
PLPGSQL. It seems
that some double characters to have value of '0x5c' in the lower byte,
making PLPGSQL to
think that the statement is a unterminatated string. And this drives me
crazy :( .

Hope someone could kindly shed some light on this.

Regards,
Frankie Lam





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: PLPGSQL with Multibyte Issue
@ 2003-03-18 07:49  Tatsuo Ishii <t-ishii@sra.co.jp>
  parent: Frankie Lam <frankie@ucr.com.hk>
  1 sibling, 1 reply; 4+ messages in thread

From: Tatsuo Ishii @ 2003-03-18 07:49 UTC (permalink / raw)
  To: frankie@ucr.com.hk; +Cc: pgsql-sql

石井です.

> I'm experiencing some problem with using multibyte character issues in
> PLPGSQL. It seems
> that some double characters to have value of '0x5c' in the lower byte,
> making PLPGSQL to
> think that the statement is a unterminatated string. And this drives me
> crazy :( .

What kind of database encoding are you using?
--
Tatsuo Ishii



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: PLPGSQL with Multibyte Issue
@ 2003-03-18 08:35  Frankie Lam <frankie@ucr.com.hk>
  parent: Frankie Lam <frankie@ucr.com.hk>
  1 sibling, 0 replies; 4+ messages in thread

From: Frankie Lam @ 2003-03-18 08:35 UTC (permalink / raw)
  To: pgsql-sql

At the beginning, I used the SQL_ASCII database encoding and found it is not
working
now, I'm using the EUC_TW as the database encoding,
and using ODBC to connect to the database, excute the plpgsql functions.
(and I'm having
SET CLIENT_ENCODING TO 'BIG5' in the connection string).

everything seems to be fine now,
but I'm still worrying if there's any loopholes there... :-(
(Too scarey to find another `truth' about the shortcoming of plpgsql)

So if anyone has similar experience, please let me know.

Thanks so much.

BTW, if I want to insert a single slash character, `\' , do I have to use
'\\\\' (that's totally 4 slashes)
inorder to  `EXCUTE' DYNAMIC plpgsql query? (sorry for my poor explanation)
e.g.
    str := '' insert into test values(''''\\\\'''');'' -- I've tried putting
\\, it doesn't work, how come it is so?
    excute str;


"Frankie Lam" <frankie@ucr.com.hk> wrote in message
news:b56hgd$2o8i$1@news.hub.org...
> Hi all,
>
> I'm experiencing some problem with using multibyte character issues in
> PLPGSQL. It seems
> that some double characters to have value of '0x5c' in the lower byte,
> making PLPGSQL to
> think that the statement is a unterminatated string. And this drives me
> crazy :( .
>
> Hope someone could kindly shed some light on this.
>
> Regards,
> Frankie Lam
>
>





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: PLPGSQL with Multibyte Issue
@ 2003-03-18 08:37  Tatsuo Ishii <t-ishii@sra.co.jp>
  parent: Tatsuo Ishii <t-ishii@sra.co.jp>
  0 siblings, 0 replies; 4+ messages in thread

From: Tatsuo Ishii @ 2003-03-18 08:37 UTC (permalink / raw)
  To: frankie@ucr.com.hk; +Cc: pgsql-sql

> [Japanese characters inserted]

Oops. I have accidentally inserted non-English characters. Please
ignore it.
--
Tatsuo Ishii



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2003-03-18 08:37 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-03-18 07:24 PLPGSQL with Multibyte Issue Frankie Lam <frankie@ucr.com.hk>
2003-03-18 07:49 ` Tatsuo Ishii <t-ishii@sra.co.jp>
2003-03-18 08:37   ` Tatsuo Ishii <t-ishii@sra.co.jp>
2003-03-18 08:35 ` Frankie Lam <frankie@ucr.com.hk>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox