Lobotomy stitches came loose again. D'oh! Different table names...
Cheers,
Ed Loehr
Ed Loehr wrote:
>
> The following drop fails due to non-existent trigger, but then the
> subsequent create fails due to existing trigger. What's happening?
> Is this a known problem?
>
> Pg 6.5.2, RH6.1, 2.2.12-20smp, Pentium III i686
>
> (from my postgres server log...)
> 20000128.13:21:05.881 [2810] query: DROP TRIGGER
> ems_user_insert_trigger ON employee;
> 20000128.13:21:05.881 [2810] ProcessUtility: DROP TRIGGER
> ems_user_insert_trigger ON employee;
> 20000128.13:21:05.881 [2810] ERROR: DropTrigger: there is no trigger
> ems_user_insert_trigger on relation employee
> 20000128.13:21:05.882 [2810] query: CREATE TRIGGER
> ems_user_insert_trigger AFTER INSERT ON ems_user FOR EACH ROW EXECUTE
> PROCEDURE add_bad_passwd_rec();
> 20000128.13:21:05.882 [2810] ProcessUtility: CREATE TRIGGER
> ems_user_insert_trigger AFTER INSERT ON ems_user FOR EACH ROW EXECUTE
> PROCEDURE add_bad_passwd_rec();
> 20000128.13:21:05.883 [2810] ERROR: CreateTrigger: trigger
> ems_user_insert_trigger already defined on relation ems_user
>
> Cheers,
> Ed Loehr