| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deprecation |
| Date: | 2009-10-17 01:23:12 |
| Message-ID: | 407d949e0910161823l6199e42fmc8d34d5a7528aa21@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 16, 2009 at 12:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> However, if the columnref looks like "x.y" where x happens to
> match some table in the database (and not in the query) that doesn't
> have a column y, the implicit-RTE code will have already modified the
> querytree before finding out that column y doesn't exist.
Hm, so if you do nothing then really the only thing that doesn't work
is if you have add_missing_from then plpgsql record variables wouldn't
work when you tried to reference their columns?
Perhaps we could just document that add_missing_from breaks that case?
The worst thing about that is that someone could switch that option on
globally on their server and break code that's part of some
third-party module.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-10-17 01:38:58 | Re: contrib/plantuner - enable PostgreSQL planner hints |
| Previous Message | Magnus Hagander | 2009-10-17 00:24:57 | Re: Encoding issues in console and eventlog on win32 |