Re: [pgadmin-hackers] Trigger addition wierdness

2003-09-30 Thread Dave Page
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 30 September 2003 00:04 To: Dave Page Cc: [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] Trigger addition wierdness Dave Page wrote: Hi Andreas, I was working in a db earlier today, and added a new

Re: [pgadmin-hackers] Trigger addition wierdness

2003-09-30 Thread Dave Page
Page Cc: [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] Trigger addition wierdness Hi Dave. It is repaired in this.:-) Please Apply it. regards, Hiroshi Saito From: Dave Page [EMAIL PROTECTED] (snip) I was working in a db earlier today, and added a new trigger to a table

Re: [pgadmin-hackers] Trigger addition wierdness

2003-09-30 Thread Dave Page
] Trigger addition wierdness Hi Dave. The humor of today's cvs is ill.:-) regards, Hiroshi Saito From: Dave Page [EMAIL PROTECTED] (snip) Hmm, shouldn't be a bug, the exterminator said he got all of those last week... I'll have to have a play. Meanwhile, I'm hacking the Query

Re: [pgadmin-hackers] Trigger addition wierdness

2003-09-30 Thread Hiroshi Saito
Hi Dave. It is repaired in this.:-) Please Apply it. regards, Hiroshi Saito From: Dave Page [EMAIL PROTECTED] (snip) I was working in a db earlier today, and added a new trigger to a table that already had one. When the new node was added to the treeview, it took the name of the

[pgadmin-hackers] Trigger addition wierdness

2003-09-29 Thread Dave Page
Hi Andreas, I was working in a db earlier today, and added a new trigger to a table that already had one. When the new node was added to the treeview, it took the name of the existing trigger, not the new one. A refresh cleared it up. I had a quick look at the code but couldn't see anything

Re: [pgadmin-hackers] Trigger addition wierdness

2003-09-29 Thread Andreas Pflug
Dave Page wrote: Hi Andreas, I was working in a db earlier today, and added a new trigger to a table that already had one. When the new node was added to the treeview, it took the name of the existing trigger, not the new one. A refresh cleared it up. I had a quick look at the code but couldn't