| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Trevor Talbot <quension(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: text search vs schemas |
| Date: | 2007-08-17 14:59:45 |
| Message-ID: | 20070817145945.GF20103@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 17, 2007 at 10:42:09AM -0400, Tom Lane wrote:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > I'm unsure how it works now, but it seems reasonable that when a
> > regclass/regtype/regetc is passed to a trigger, pass it in OID form.
>
> If you insist on a solution that involves attaching type information
> to trigger arguments, then we can forget about getting tsearch into 8.3.
> That's a nontrivial amount of new design and code that hasn't even been
> on the radar screen before.
Hmm, maybe I didn't explain clearly enough. I meant that if the
argument is a regclass for example, to pass it in the TG_ARGV list as
the OID in *string form*.
That way trigger arguments stay a list of strings, yet the whole thing
is schema safe because when trigger body casts the string back to a
regclass, it gets exactly what was passed.
Hope this makes more sense,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-17 15:09:29 | Re: tsearch2 in PostgreSQL 8.3? |
| Previous Message | Bruce Momjian | 2007-08-17 14:58:28 | Re: tsearch2 in PostgreSQL 8.3? |