pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
plpgsql bug(?)
2+ messages / 2 participants
[nested] [flat]

* plpgsql bug(?)
@ 2000-01-05 10:25 Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>
  2000-01-05 15:05 ` Re: [SQL] plpgsql bug(?) Jan Wieck <wieck@debis.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Kovacs Zoltan @ 2000-01-05 10:25 UTC (permalink / raw)
  To: wieck@debis.com; +Cc: pgsql-sql

Dear Jan,

I have started to use plpgsql language for triggers (especially
for 'UPDATE AFTER' ones). It works very good, except the following:

CREATE FUNCTION "partner_t22" ( ) RETURNS opaque AS 
'begin if new.az != old.az then update vevõ_megrendelése 
set vevõ = new.az where vevõ = old.az; end if; return new; end;'
LANGUAGE 'plpgsql';

After UPDATE, I am running into:

ERROR:  record new has no field vev

The problem occurs with "vevõ = new.az", I think the plpgsql parser
stops processing the field name "vevõ" because "õ" (code 245)
is not a standard ASCII character, it is from the Latin2 set.
I tried other non-international characters like "é" (code 233)
without success.

Could you please help, where to modify the sources to make this work?
I am using version 6.5.2.

Thank you in advice,
best wishes,
			    Kovacs, Zoltan





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

* Re: [SQL] plpgsql bug(?)
  2000-01-05 10:25 plpgsql bug(?) Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>
@ 2000-01-05 15:05 ` Jan Wieck <wieck@debis.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Jan Wieck @ 2000-01-05 15:05 UTC (permalink / raw)
  To: Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>; +Cc: pgsql-sql

Kovacs Zoltan wrote:

> Dear Jan,
>
> The problem occurs with "vevõ = new.az", I think the plpgsql parser
> stops processing the field name "vevõ" because "õ" (code 245)
> is not a standard ASCII character, it is from the Latin2 set.
> I tried other non-international characters like "é" (code 233)
> without success.
>
> Could you please help, where to modify the sources to make this work?
> I am using version 6.5.2.

     Unfortunately I cannot reproduce that behaviour here. Seems
     that your version of lex(1) has another understanding of the
     character class [:alnum:] than my one. I can use äöü
     (a-diaeresis etc.), µ (greek my character) and ³ (3
     superscripted) too.

     I'm using flex-2.5.4 here. But I'm not really sure it is that
     itself, maybe flex is using isalnum() from the standard C
     library inside. Then it would be more tricky.

     You can play around with the two character sets WS and WC
     declared at the top of

     src/pl/plpgsql/src/scan.l

     They are slightly extended regular expressions (the class
     notation inside).



Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #






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


end of thread, other threads:[~2000-01-05 15:05 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-01-05 10:25 plpgsql bug(?) Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>
2000-01-05 15:05 ` Jan Wieck <wieck@debis.com>

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