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

Re: BUG #5676: When creating a trigger an dummy argument is inserted.

From: Christopher A Hotchkiss <christopher(dot)a(dot)hotchkiss(at)jpmchase(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5676: When creating a trigger an dummy argument is inserted.
Date: 2010-09-24 16:05:21
Message-ID: 661872841ED1D04784B470897CDBFAF40C1FFA4ED4@EMARC132VS01.exchad.jpmchase.net (view raw or flat)
Thread:
Lists: pgsql-bugs
Thanks Tom,
I will report it to them.

Christopher A Hotchkiss
JPMorgan Chase & Co. - Navy Cash Application Developer
Email christopher(dot)a(dot)hotchkiss(at)jpmchase(dot)com

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: Friday, September 24, 2010 12:04 PM
To: Christopher A Hotchkiss
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #5676: When creating a trigger an dummy argument is inserted. 

"Christopher Hotchkiss" <christopher(dot)a(dot)hotchkiss(at)jpmchase(dot)com> writes:
> When creating the following trigger:

> CREATE TRIGGER c_aud_trg
>   BEFORE INSERT OR UPDATE OR DELETE
>   ON ca
>   FOR EACH ROW
>   EXECUTE PROCEDURE c_aud_trg_trfunc();

> It will actually get created as (using pgAdmin 1.12):
> CREATE TRIGGER c_aud_trg
>   BEFORE INSERT OR UPDATE
>   ON ca
>   FOR EACH ROW
>   EXECUTE PROCEDURE c_aud_trg_func(E'\\x');

> If that same trigger is dropped and re-added using what is in the database,
> the following shows up:
> CREATE TRIGGER c_aud_trg
>   BEFORE INSERT OR UPDATE
>   ON ca
>   FOR EACH ROW
>   EXECUTE PROCEDURE c_aud_trg_func(E'\\x5c7800');

I think what you've got here is a pgAdmin bug, because I see no such
behavior using psql and pg_dump.  Suggest reporting it on the pgAdmin
mailing lists.

			regards, tom lane
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.

In response to

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2010-09-24 16:35:21
Subject: Re: installer problems
Previous:From: Tom LaneDate: 2010-09-24 16:03:35
Subject: Re: BUG #5676: When creating a trigger an dummy argument is inserted.

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