I've got a series of triggers that are responsible for maintaining
deduced data in a table (background for this can be found in an
earlier mailing list posting: http://archives.postgresql.org/pgsql-sql/2008-10/msg00041.php)
.
This problem concerns the order in which my triggers are executed.
On Oct 10, 2008, at 5:16 PM, Christopher Maier wrote:
On Oct 10, 2008, at 4:53 PM, Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Looks like you should revoke DELETE privilege from plain users, and
have your delete trigger be a security definer function. There
would be
anothe
"Christopher Maier" <[EMAIL PROTECTED]> writes:
> ... Based on debugging messages I added
> to the triggers, it looks like the before row triggers fire for ALL
> the rows first, THEN all the after row triggers fire.
That's correct. After triggers are queued up and fired at end of
statement.
-- Original message --
From: "Christopher Maier" <[EMAIL PROTECTED]>
>
> As you can see, doing a row-by-row delete works fine, but when doing a
> bulk delete, all the before triggers are grouped together, as are all
> the after triggers.
>
> Why are these ca
Hello all, I'm still new to postgres
If I have 2 tables with the following data structure
Agentno and agentname (along with many other fields) this table is called
agent_master
And I have another table with agentno and agentname. Table called
updatetable
When I add data in the updateta
On Mon, Oct 13, 2008 at 1:23 PM, Chris Preston
<[EMAIL PROTECTED]> wrote:
> Hello all, I'm still new to postgres
>
> If I have 2 tables with the following data structure
>
> Agentno and agentname (along with many other fields) this table is called
> agent_master
>
> And I have another table with ag
On Oct 13, 2008, at 3:08 PM, Adrian Klaver wrote:
-- Original message --
From: "Christopher Maier" <[EMAIL PROTECTED]>
As you can see, doing a row-by-row delete works fine, but when
doing a
bulk delete, all the before triggers are grouped together, as are
