On Wed, Oct 22, 2014 at 11:21 AM, Pavel Stehule <pavel.steh...@gmail.com> wrote: > Hi > > with new functions row_to_json(b), there is more often usage of ROW > constructor. Using names in fields is relative difficult. Because ROW has > special clause in parser, I am thinking so we can enable labeling inside ROW > constructor > > so instead currently supported: > > select row_to_json(r) from (select 10 as a, 20 as b) r; > > users can to write: > > select row_to_json(row(10 as a,20 as b)); > > labeling will be enabled "only" inside ROW constructor. I don't propose > enable it everywhere. > > What do you think about it?
It's a neat idea -- maybe a better alternative to what I was thinking here: http://postgresql.1045698.n5.nabble.com/Support-UPDATE-table-SET-tp5823073p5823944.html Some questions: *) What would the parser transformation resolve to *) Are we ok with SQL standard *) Do you think this (or some similar variant) would work? select row_to_json(row(foo.*)) from foo; merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
