Skip site navigation (1) Skip section navigation (2)

Re: BUG #1767: Trigger handling

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: THILANKA <tilankaedu(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1767: Trigger handling
Date: 2005-07-15 21:56:48
Message-ID: c2d9e70e0507151456464c39ed@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On 7/13/05, THILANKA <tilankaedu(at)yahoo(dot)com> wrote:
> 
> The following bug has been logged online:
> 
> Bug reference:      1767
> Logged by:          THILANKA
> Email address:      tilankaedu(at)yahoo(dot)com
> PostgreSQL version: suse 9.0 builti
> Operating system:   SUSE LINUX
> Description:        Trigger handling
> Details:
> 
> Here is the my question.
> 
> I tried to pass parameters to the trigger using "new" key word, but it's not
> accepted. The purpose of doing that i want to pass some data to a "c" file
> and to send the same data into a another database. So in that problem i
> faild. If u know how to do that pls send me the way.
> 

Triggers doesn't accept parameters at runtime. 

taken from: http://www.postgresql.org/docs/8.0/static/sql-createtrigger.html

CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }
    ON table [ FOR [ EACH ] { ROW | STATEMENT } ]
    EXECUTE PROCEDURE funcname ( arguments )

arguments
An optional comma-separated list of arguments to be provided to the
function when the trigger is executed. The arguments are literal
string constants. Simple names and numeric constants may be written
here, too, but they will all be converted to strings. Please check the
description of the implementation language of the trigger function
about how the trigger arguments are accessible within the function; it
may be different from normal function arguments.

-- 
Atentamente,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

In response to

pgsql-bugs by date

Next:From: sivagopalDate: 2005-07-16 12:00:24
Subject: BUG #1772: java.sql.SQLException
Previous:From: Dr. Volker GoebbelsDate: 2005-07-15 17:29:36
Subject: Re: [postgres] An den Admin

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group