Re: Weird in PGAdmin behavior for triggers of the same kind.

I beleive this has been fixed already - can you try the latest version
from www.pgadmin.org please.

Regards, Dave

> -----Original Message-----
> From: Ludwig Lim [mailto:lud_nowhere_man@yahoo.com]
> Sent: 15 November 2002 11:19
> To: PGAdmin Support Mailing List
> Subject: [pgadmin-support] Weird in PGAdmin behavior for
> triggers of the same kind.
>
>
> Hi:
>
>   I am experiencing a weird problem having with
> PGAdmin when I am viewing the body of the 2 triggers
> of the same kind (2 AFTER UPDATE triggers):
>
>   The following is what I get from screen :
> -- Trigger: tu_sc_redeem ON sc_redeem
> CREATE TRIGGER "tu_sc_redeem" AFTER INSERTUPDATE ON
> "sc_redeem"
> FOR EACH ROW EXECUTE PROCEDURE f_tu_sc_redeem();
>
> -- Trigger: tu_sc_redeem_fspdet ON sc_redeem
> CREATE TRIGGER "tu_sc_redeem_fspdet" AFTER
> INSERTUPDATEUPDATE ON "sc_redeem"
> FOR EACH ROW EXECUTE PROCEDURE
> f_tu_sc_redeem_fspdet();
>
>     Note that the INSERTUPDATE and INSERTUPDATEUPDATE
> are not  typos. I just copy and paste it from the
> "definition window" in PGAdmin
>
>    I tried to drop and recreate the trigger in psql
> (after making that both of are AFTER UPDATE TRIGGERS
> only)  but still the same thing happened. This
> phenomena has not occured on tables having more than
> triggers of diffrent type.
>
>     I hope the following might be of some help:
>
> SELECT  tgname,tgtype
> FROM pg_trigger
> WHERE tgname IN
> ('tu_sc_redeem_fspdet','tu_sc_redeem');
>
>        tgname        | tgtype
> ---------------------+--------
>  tu_sc_redeem        |     17
>  tu_sc_redeem_fspdet |     17
>
> PGAdmin version : PGAdmin II v 1.2.0
>
> Thank you in advance,
> ludwig.
>
>
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
http://archives.postgresql.org