From: | Michael Gould <mgould(at)intermodalsoftwaresolutions(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Issue with insert |
Date: | 2010-02-27 21:02:06 |
Message-ID: | e58f6475e92a90670fcc7e02d518f099@intermodalsoftwaresolutions.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Tom,
Thanks, that's exactly what it was.
Best Regards
Mike Gould
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Gould <mgould(at)intermodalsoftwaresolutions(dot)net> writes:
>> Here is the table DDL,
>
> Can't really test this since you didn't supply the source code for
> those triggers:
>
>> CREATE TRIGGER "insertcitystateinfo" BEFORE INSERT OR UPDATE
>> ON "iss"."citystateinfo" FOR EACH ROW
>> EXECUTE PROCEDURE "iss"."insertcitystateinfofunc"();
>
>> CREATE TRIGGER "update_timestamp_citystateinfo" BEFORE UPDATE
>> ON "iss"."citystateinfo" FOR EACH ROW
>> EXECUTE PROCEDURE "iss"."timestampfunc"();
>
> Personally I'm suspicious that the BEFORE INSERT trigger is changing the
> data.
>
> regards, tom lane
>
--
Michael Gould, Managing Partner
Intermodal Software Solutions, LLC
904.226.0978
904.592.5250 fax
From | Date | Subject | |
---|---|---|---|
Next Message | rawi | 2010-03-01 10:07:08 | kind of RULE on SELECT depending on existence of a WHERE condition |
Previous Message | Tom Lane | 2010-02-27 20:58:20 | Re: Issue with insert |