Jeff Frost wrote:
>
>> Another problem might well be with your plpgsql trigger function. If
>> you're dropping/re-creating credit_card_audit then that'll give you
>> the error you're seeing.
>
> The trigger shouldn't be firing at all in this scenario as it is on
> credit_card and not credit_card_audit. Are you saying that it could
> cause this sort of problem even though it doesn't fire?
Actually, my last reply isn't quite accurate. Looking at it, you do
update "credit_card_audit" from within the trigger.
So, it can cause a problem if called, but if it isn't called then it
will not.
-- Richard Huxton Archonet Ltd
