| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <janwieck(at)yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RI triggers and schemas |
| Date: | 2002-04-01 17:42:20 |
| Message-ID: | 20020401093707.J23284-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 1 Apr 2002, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > Well, there is another place where the current name behavior
> > causes problems so we'd need to be sticking in the fully qualified
> > name, otherwise creating a table in your search path earlier than
> > the intended table would break the constraint. This currently already
> > happens with temp tables.
>
> But the point is that the table name would be resolved to OID once at
> CREATE TRIGGER time (or when the original FK constraint is created).
> After that, it's up to the trigger to construct queries using the
> fully-qualified table name. This should eliminate the temp table
> gotcha as well as change-of-search-path issues.
Sorry, I must have misunderstood you. I thought you were backing away
from changing the arguments that were created for the trigger. Or did
you mean using the stored info on the two oids we already have in the
record (tgrelid and tgconstrrelid)?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-01 17:48:45 | Re: timeout implementation issues |
| Previous Message | Tom Lane | 2002-04-01 17:19:14 | Re: RI triggers and schemas |