| From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Trigger display bug |
| Date: | 2002-02-20 12:52:39 |
| Message-ID: | FED2B709E3270E4B903EB0175A49BCB10475CA@dogbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 20 February 2002 11:44
> To: pgadmin-hackers(at)postgresql(dot)org
> Cc: Dave Page
> Subject: [pgadmin-hackers] Trigger display bug
>
>
> Dear Dave,
>
> CREATE TRIGGER "tg_term_source_iu" BEFORE DELETEINSERT OR UPDATE ON
> "translationforge_term_source" FOR EACH ROW EXECUTE PROCEDURE
> tg_term_source_iu();
>
> The properties of the trigger appear to be OK. Only the SQL
> definition does
> not display well. I tried to understand the bug but did not
> succeed. Is this
> an hbx display bug?
No, pgSchema (not clearing a variable in a loop). Fixed in CVS now, thanks
for the report.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-02-20 13:22:56 | Re: To-Do List |
| Previous Message | Jean-Michel POURE | 2002-02-20 11:44:14 | Trigger display bug |