SPI_modifytuple - why i cant use it in trigers fired after

From: Marek Bartnikowski <marek(at)virt(dot)pl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: SPI_modifytuple - why i cant use it in trigers fired after
Date: 2001-10-22 08:46:22
Message-ID: Pine.LNX.4.21.0110221041190.2226-100000@easy
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


fragment from PostgreSQL 7.1 Documentation:
"Trigger functions return HeapTuple to the calling Executor. This is
ignored for triggers fired after an INSERT, DELETE or UPDATE operation but
it allows BEFORE triggers to: ......"

can somebody tell my why ? is it bug or what ?
sometimes i have to use it AFTER insert, update or delete. what can i do
in this situation.

thank you in advance

--
Marek Bartnikowski <mailto:marek(at)virt(dot)pl>
PostgreSQL DBA
C, PHP Prog.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Storah 2001-10-22 08:52:16 Re: ODBC driver and non case-insensitivity?
Previous Message Tom Lane 2001-10-20 03:41:19 Re: Bug #488: Apache daemon dying on segfault from postgres