| From: | Rafal Pietrak <rafal(at)zorro(dot)isa-geek(dot)com> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | Steve Haresnape <s(dot)haresnape(at)creativeintegrity(dot)co(dot)nz>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: RFE: Column aliases in WHERE clauses |
| Date: | 2012-09-19 13:03:22 |
| Message-ID: | 1348059802.21898.275.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2012-09-19 at 20:36 +0800, Craig Ringer wrote:
> On 09/19/2012 02:36 PM, Steve Haresnape wrote:
>
> > Since some dialects support the idiom and others don't there can't be
> > any compelling reason to withhold support. It's really a matter of style.
> > For my money the DRY style is better.
>
> So you're saying that you want the implementation to effectively clone
> the aliased SELECT term into the WHERE clause?
>
> If so, what about functions with side-effects?
What about them: if they are put in the where clause by the user - e.g.
not from unaliasing?
Just bug-traceing will be more difficult from alias obfuscating effects.
That's all.
-R
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2012-09-19 13:15:56 | Re: RFE: Column aliases in WHERE clauses |
| Previous Message | Craig Ringer | 2012-09-19 12:39:16 | Re: drop table if exists <VIEW_NAME>; |