check out this link. I it will be what you are looking for
http://errorbank.blogspot.com/2011/03/list-all-foreign-keys-references-for.html
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Multiple-foreign-keys-with-the-same-name-and-information-schema-tp1921901p4303625.ht
>
> Actually, the information_schema supposes that constraint names are
> unique within a *schema*, not within a *catalog* (a/k/a database).
> Don't know if that distinction can help you or not. You are correct
> that Postgres is less rigid. We do not consider that to be a deficiency
> on the Pos
Jonathan Tapicer writes:
> I was a able to do it using the pg_catalog tables, but I haven't found
> a way to do it using information_schema since it relies on foreign
> keys names being unique in the same catalog. Is this a known
> limitation?
Actually, the information_schema supposes that constr
Hello everyone, I have a question regarding foreign keys and
information_schema. Given the following valid schema:
CREATE TABLE "Cat"
(
"IdCat" serial NOT NULL,
CONSTRAINT "PK_Cat" PRIMARY KEY ("IdCat")
);
CREATE TABLE "Art"
(
"IdArt" serial NOT NULL,
"IdCat" integer NOT NULL,
CONSTRAIN
On Mon, 13 Dec 2004 23:00:45 -0700 Michael Fuhr <[EMAIL PROTECTED]> wrote:
> Do you mean that you don't need foreign key constraints to enforce
> referential integrity, but only to cascade changes to another table?
> If so, have you considered using triggers instead? Or have I
> misunderstood what
On Tue, Dec 14, 2004 at 02:06:24AM +0200, Ciprian Popovici wrote:
> I'm in a situation where it would be useful to bind a field in a table via
> foreign keys to N other tables simultaneously. The table holds a common
> type of info which all those other tables use. The many tables refer to the
> c
On Tue, Dec 14, 2004 at 02:06:24 +0200,
Ciprian Popovici <[EMAIL PROTECTED]> wrote:
> I'm in a situation where it would be useful to bind a field in a table via
> foreign keys to N other tables simultaneously. The table holds a common
> type of info which all those other tables use. The many tabl
I'm in a situation where it would be useful to bind a field in a table via
foreign keys to N other tables simultaneously. The table holds a common
type of info which all those other tables use. The many tables refer to the
common table by keeping references to its serial field.
By doing this, I co
I was wondering if there is any way to set up a foreign key that is
valid not just if the value exists in one table but if it exists in any
of 3 tables. Here is what I mean. I have a sequence called 'id_number'
that I start at 1 and increment by 1 every time its used. I then have 3
tables each
