> -Original Message-
> From: Ivan [mailto:[EMAIL PROTECTED]
> Sent: 20 May 2005 10:01
> To: Dave Page
> Cc: pgadmin-support@postgresql.org
> Subject: Re[2]: [pgadmin-support] Bug in CHECK constraints
> statement reverse engineering.
>
> You were right
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
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ivan
> Sent: 19 May 2005 16:37
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Bug in CHECK constraints statement
> reverse engineering.
>
> Hello,
Hello,
PgAdmin 1.3.0 (Apr 24 2005)
Wrong CHECK reverse engineering.
In PostgreSQL documentation i found:
--
41.10. pg_constraint
Note
consrc is not updated when referenced objects change; for example,
it won't track renaming of
