"Pavel Stehule" <pavel.steh...@gmail.com> writes: > 2008/12/12 Heikki Linnakangas <heikki.linnakan...@enterprisedb.com>: > >> We could do it the other way round: >> >> SELECT foo( 'ick' AS bar, 'ack' AS baz);
I always assumed we were talking about it this way. Everywhere else in SQL AS is followed by the labels, not the values. > I discussed about this form with Tom. > > I thing so following should be readable: > > name: [ optional => ] value > > SELECT foo( bar: 'ick', baz: 'ack' ); > SELECT foo( bar: => 'ick', baz: => 'ack' ); > > or > > SELECT foo( bar: = 'ick', baz: = 'ack' ); > > reason for optional using of "=>" is too thin char ":", so => > optically boost the colon. These don't solve anything. There's nothing stopping you from defining a unary prefix operator => or = In any case this is all weird. SQL isn't C and doesn't have random bits of punctuation involved in syntax. It uses whole words for just about everything. Anything you do using punctuation characters is going to look out of place. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
