Re: Bug in CHECK constraints statement reverse engineering.

> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Ivan
> Sent: 19 May 2005 16:37
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] Bug in CHECK constraints statement
> reverse engineering.
>
> Hello,
>
> PgAdmin 1.3.0 (Apr 24 2005)
> Wrong CHECK reverse engineering.

Hi,

pgAdmin does do this correctly. In order to run at a reasonable speed,
pgAdmin caches details of objects read from the database, rather than
running queries every time you select one. If you rename an object such
as a function, it doesn't always know that that action may cause a
property of another object to be changed, thus pgAdmin may continue to
show the old definition.

To force a reload, right-click a node in the treeview and select the
'Refresh' option.

>
> It will be convenient for me if the first line will be
>
> -- Function: "Check_IntegerGreaterZero"("in_Value" int4)
>
> - quoted function name and argument names. It is useful for
> copy / paste purposes :)

Thanks, fix commited.

Regards, Dave