trigger AFTER INSERT

am 12.08.2010 16:58:53 von josiperez3t

--0016367b6c30caea42048da19a18
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I think that I have a conceptual problem and I hope anyone could help me.

If I write a trigger AFTER INSERT and I have one error in this trigger, the
record (that I think was already inserted) is not inserted.
Example:

INSERT INTO tableX
trigger sumRecords AFTER INSERT under tableX to accumulate the records
inserted by hour
if there is an error in the commands executed for this record, is
not in the tableX

If this occurs in a trigger BEFORE INSERT, I can understand, but, if it is
AFTER INSERT, I believe that the record is already inserted.
What is wrong on it?

Thanks in advance
Josi Perez

--0016367b6c30caea42048da19a18
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

I think that I have a conceptual problem and I hope anyone could=
help me.

If I write a trigger AFTER INSERT and I have one error in =
this trigger, the record (that I think was already inserted) is not inserte=
d.

Example:

INSERT INTO tableX <record1>
trigger sumRecords AF=
TER INSERT under tableX to accumulate the records inserted by hour
if th=
ere is an error in the commands executed for this record, <record1> i=
s not in the tableX

If this occurs in a trigger BEFORE INSERT, I can understand, but, if it=
is AFTER INSERT, I believe that the record is already inserted.
What is=
wrong on it?

Thanks in advance
Josi Perez

ility: hidden; display: inline;" id=3D"avg_ls_inline_popup">

--0016367b6c30caea42048da19a18--

Re: trigger AFTER INSERT

am 12.08.2010 17:00:26 von Tom Lane

"Josi Perez (3T Systems)" writes:
> If I write a trigger AFTER INSERT and I have one error in this trigger, the
> record (that I think was already inserted) is not inserted.

Sure, because the whole transaction is rolled back on error.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Re: trigger AFTER INSERT

am 16.08.2010 18:06:29 von josiperez3t

--0022152d7c5bed2add048df30333
Content-Type: text/plain; charset=ISO-8859-1

Thank you for your answer.
Without considering the errors, the transaction should not start after the
AFTER INSERT?
Josi Perez

2010/8/12 Tom Lane

> "Josi Perez (3T Systems)" writes:
> > If I write a trigger AFTER INSERT and I have one error in this trigger,
> the
> > record (that I think was already inserted) is not inserted.
>
> Sure, because the whole transaction is rolled back on error.
>
> regards, tom lane
>

--0022152d7c5bed2add048df30333
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thank you for your answer.
=
Without considering the errors, the transaction=
should not start after the AFTER INSERT?
Josi Perez
r>

2010/8/12 Tom Lane < =3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us>
te class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1=
px solid rgb(204, 204, 204); padding-left: 1ex;">

"Josi Perez (3T Systems)" < :josiperez3t@gmail.com">josiperez3t@gmail.com> writes:

> If I write a trigger AFTER INSERT and I have one error in this trigger=
, the

> record (that I think was already inserted) is not inserted.

Sure, because the whole transaction is rolled back on error.

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0regards, tom lane

id=3D"avg_ls_inline_popup">

--0022152d7c5bed2add048df30333--

Re: trigger AFTER INSERT

am 16.08.2010 18:39:27 von Kevin Grittner

"Josi Perez (3T Systems)" wrote:

> Without considering the errors, the transaction should not start
> after the AFTER INSERT?

Anything happening in a trigger is always part of the same database
transaction as the database action which fired the trigger.

-Kevin

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin