Re: [GENERAL] How to enumerate foreign key constraints after

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Forest Wilkinson <lyris-pg(at)tibit(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] How to enumerate foreign key constraints after
Date: 2003-06-11 20:01:15
Message-ID: 1055361674.49179.3.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> >Yes, a combination of the two would probably be better. You would need
> >to be careful about function call names for FKeys, there are a fair
> >number of them. Checking for 3 triggers with the function name starting
> >with RI_FKey* would probably be better.
>
> Will the tgisconstraint flag always be set for these triggers? Will
> the function names still be RI_FKey* once these databases are migrated
> to postgres 7.4 or later?

Until someone has a good reason to change things, they'll probably stay
the same, so you will probably get a release or two out of it.

But it is much easier to change the internal structures now, as
PostgreSQL doesn't have nearly as much of a backward compatibility issue
anymore.

--
Rod Taylor <rbt(at)rbt(dot)ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2003-06-11 20:05:16 Re: tsearch v2
Previous Message Kaarel 2003-06-11 19:57:59 Re: Postgres performance comments from a MySQL user

Browse pgsql-hackers by date

  From Date Subject
Next Message Dann Corbit 2003-06-11 20:05:26 Re: Postgres performance comments from a MySQL user
Previous Message Bruce Momjian 2003-06-11 19:31:03 Re: Please, apply patch for current CVS