plpgsql bug(?)

From: Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu>
To: wieck(at)debis(dot)com
Cc: pgsql-sql(at)postgresql(dot)org
Subject: plpgsql bug(?)
Date: 2000-01-05 10:25:23
Message-ID: Pine.LNX.4.05.10001051123380.19358-100000@pc10.radnoti-szeged.sulinet.hu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_megrendelse
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

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Jan Wieck 2000-01-05 15:05:31 Re: [SQL] plpgsql bug(?)
Previous Message Tom Lane 2000-01-05 05:35:03 Re: [SQL] Calculation dependencies in views