| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Patrick Samson <p_samson(at)Yahoo(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: pltcl - "Cache lookup for attribute" error - version 2 |
| Date: | 2004-01-23 19:38:51 |
| Message-ID: | 29558.1074886731@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> When assigning a tuple to an array, PL/Tcl creates one extra array
> element .tupno telling the SPI_tuptable index of the result tuple. I
> think I originally planned to have more of these critters ... but
> probably never really needed them. It is in there since 6.3!
> Bottom line is, if one has a trigger, and inside the trigger he does an
> SPI_exec, fetches a tuple into an array and then returns [array get x]
> instead of new or old ... so from the back through the right chest into
> the left eye ... then it will fail if the .tupno isn't filtered out.
Hm. Perhaps we should tighten the test to reject only ".tupno", rather
than any name starting with dot?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-01-23 20:03:59 | Re: pltcl - "Cache lookup for attribute" error - version |
| Previous Message | Jan Wieck | 2004-01-23 17:37:52 | Re: pltcl - "Cache lookup for attribute" error - version |