Re: Bug in CHECK constraints statement reverse engineering.

Hello Dave,

DP> Hi,

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

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

You were right on a half - pgAdmin do this correctly for tables check
constraints, but for domain definition 'Refresh' and even closing
pgAdmin and restarting postmaster doesn't help :) -
I see:

CREATE DOMAIN "TestDomain"
AS int4
CONSTRAINT TestDomain_check CHECK "Check_IntegerGreaterZero"(VALUE);

though function were renamed.

By the way it will be great to add quoting of domain's constraint name
in the definition pane (right bottom).

Thank you for support.

--
Best regards,
Ivan mailto:Ivan-Sun1(at)mail(dot)ru