| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Missing array support |
| Date: | 2003-06-30 21:05:45 |
| Message-ID: | 3F00A629.8020905@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> If only ANYELEMENT and not ANYARRAY appears in a function declaration,
> then it can stand for any type, because only rule 2 applies. (The
> difference from ANY is that multiple occurences of ANYELEMENT are all
> constrained to stand for the same type.)
Hmmm, I don't remember that nuance, hence the code deficiency. I'm
should be able to finish up the plpgsql hash table stuff in the next
couple of hours, then I'll get back to thinking about this one. Do I
have until midnite PDT, or EDT?
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2003-06-30 21:11:57 | Re: PlPython |
| Previous Message | Stephan Szabo | 2003-06-30 21:00:05 | Re: Is Patch Ok for deferred trigger disk queue? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2003-06-30 21:09:29 | Re: Fix getXXX methods when used with CHAR columns or |
| Previous Message | Tom Lane | 2003-06-30 20:50:21 | Re: [HACKERS] Missing array support |