From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | <pgsql-patches(at)postgresql(dot)org> |
Subject: | Get constrrelid for fk constraints that lost it |
Date: | 2002-09-30 05:01:34 |
Message-ID: | 20020929213738.N75495-200000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
I believe this should allow create constraint trigger
to look up the constrrelid out of the fk constraint
arguments for those cases where the FROM clause
was lost if we want to go that route.
It determines if it should look up args and which
argument to use based on the function name and won't
probably handle delimited names nicely. I figured
that since the point of it is to read old dumps,
this is okay. If the table doesn't exist or there
aren't enough args to intuit a table name, it currently
elog errors. Is that reasonable behavior, or should
it be taking the constraint and letting it fail at
runtime?
Attachment | Content-Type | Size |
---|---|---|
constrrelid.patch | text/plain | 1.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB SD | 2002-09-30 11:59:54 | AIX compilation problems (was Re: Proposal ...) |
Previous Message | Tom Lane | 2002-09-30 03:48:18 | Re: DROP COLUMN misbehaviour with multiple inheritance |