Questionable behavior regarding aliasing - Mailing list pgsql-hackers

From Jim Nasby
Subject Questionable behavior regarding aliasing
Date
Msg-id 56182407.6020509@BlueTreble.com
Whole thread Raw
Responses Re: Questionable behavior regarding aliasing  (Marko Tiikkaja <marko@joh.to>)
Re: Questionable behavior regarding aliasing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I fat-fingered a view create and ended up with this:

...      , schemaname, relname -- other      now      , d_now, ...

I was about to report this as a bug until Marko Tiikkaja pointed out on 
IRC that now was being treated as an alias for relname.

I'm not sure if this is required by the spec, but can we at least emit a 
WARNING if not reject this case outright? I think it'd be OK to leave 
the AS syntax alone... presumably it's a lot harder to fumble that. But 
I'm not wed to that.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line
Next
From: Marko Tiikkaja
Date:
Subject: Re: Questionable behavior regarding aliasing