| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Dan S <strd911(at)gmail(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Bug in pgadmin III v 1.12.2 |
| Date: | 2011-03-13 09:54:47 |
| Message-ID: | 4D7C9467.7080001@lelarge.info |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Le 13/03/2011 10:35, Dan S a écrit :
> Hi !
>
> I'm running pgadmin v. 1.12.2 on winxp and postgres "PostgreSQL 9.0.2,
> compiled by Visual C++ build 1500, 32-bit".
>
> When selecting a table in the tree-navigator to the left the table
> definition and its triggers appears to the right.
> However the trigger definition doesn't appear to be right ( a constraint
> trigger appears as an ordinary trigger ).
>
> To reproduce:
>
> create the table and trigger below then refresh the table definition in
> pgadmin and look at the trigger.
> It is not shown as a constraint trigger !
>
Thanks for reporting this. It seems pgAdmin doesn't know anything about
constraint trigger. This is something we'll have to add in a future release.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qiqi YU | 2011-03-13 15:37:41 | Re: where are the query output tuples stored |
| Previous Message | Dan S | 2011-03-13 09:35:42 | Bug in pgadmin III v 1.12.2 |