Thread: problem with empty arguments of trigger procedure

problem with empty arguments of trigger procedure

From
Michał Sienicki
Date:
Bug report - pgAdmin 1.14.3, Windows

Trigger definition is not shown properly when function contains "empty" arguments.

Example

Trigger definition:

CREATE TRIGGER test_trigger
BEFORE INSERT
ON test_table
FOR EACH ROW
EXECUTE PROCEDURE test_function('arg1', '', 'arg3');

is displayed in pgAdmin as:

CREATE TRIGGER test_trigger
BEFORE INSERT
ON test_table
FOR EACH ROW
EXECUTE PROCEDURE test_function('arg1', 'arg3');

MS


Re: problem with empty arguments of trigger procedure

From
Guillaume Lelarge
Date:
On Tue, 2012-07-03 at 10:05 +0200, Michał Sienicki wrote:
> Bug report - pgAdmin 1.14.3, Windows
>
> Trigger definition is not shown properly when function contains "empty" arguments.
>
> Example
>
> Trigger definition:
>
> CREATE TRIGGER test_trigger
> BEFORE INSERT
> ON test_table
> FOR EACH ROW
> EXECUTE PROCEDURE test_function('arg1', '', 'arg3');
>
> is displayed in pgAdmin as:
>
> CREATE TRIGGER test_trigger
> BEFORE INSERT
> ON test_table
> FOR EACH ROW
> EXECUTE PROCEDURE test_function('arg1', 'arg3');
>

You're right, this is a bug. I added a ticket to work on it later.
Thanks for your report.


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com



Re: problem with empty arguments of trigger procedure

From
Guillaume Lelarge
Date:
On Wed, 2012-07-04 at 21:55 +0200, Guillaume Lelarge wrote:
> On Tue, 2012-07-03 at 10:05 +0200, Michał Sienicki wrote:
> > Bug report - pgAdmin 1.14.3, Windows
> >
> > Trigger definition is not shown properly when function contains "empty" arguments.
> >
> > Example
> >
> > Trigger definition:
> >
> > CREATE TRIGGER test_trigger
> > BEFORE INSERT
> > ON test_table
> > FOR EACH ROW
> > EXECUTE PROCEDURE test_function('arg1', '', 'arg3');
> >
> > is displayed in pgAdmin as:
> >
> > CREATE TRIGGER test_trigger
> > BEFORE INSERT
> > ON test_table
> > FOR EACH ROW
> > EXECUTE PROCEDURE test_function('arg1', 'arg3');
> >
>
> You're right, this is a bug. I added a ticket to work on it later.
> Thanks for your report.
>

It's fixed in 1.16.

Thank you.


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com