| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Marti Raudsepp <marti(at)juffo(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql.consistent_into |
| Date: | 2014-01-15 06:35:46 |
| Message-ID: | 13490.1389767746@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <jim(at)nasby(dot)net> writes:
> Do we actually support = right now? We already support
> v_field := field FROM table ... ;
> and I think it's a bad idea to have different meaning for = and :=.
That ship sailed a *very* long time ago. See other thread about
documenting rather than ignoring this more-or-less-aboriginal
behavior of plpgsql.
> I have no idea if this is related or not, but I would REALLY like for this to work (doesn't in 8.4, AFAIK not in 9.1 either...)
Hm ... too tired to be sure, but I think the issue about inlining a
function of this kind has to do with whether you get the same answers
in corner cases such as subselect fetching no rows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2014-01-15 06:46:28 | Re: tests for client programs |
| Previous Message | Jim Nasby | 2014-01-15 06:23:25 | Re: plpgsql.consistent_into |