Re: JSON Function Bike Shedding
От
Merlin Moncure
Тема
Re: JSON Function Bike Shedding
Дата
Msg-id
CAHyXU0xzWtxc7XCTv6e2LPoUC5GLBHtvnMOo7ys5s8O9tTLdAg@mail.gmail.com
Ответ на
Re: JSON Function Bike Shedding (Tom Lane)
Список
Дерево обсуждения
JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Josh Berkus <josh@agliodbs.com>
Re: JSON Function Bike Shedding Tom Lane <tgl@sss.pgh.pa.us>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@kineticode.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding David E. Wheeler <david@justatheory.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding Alvaro Herrera <alvherre@2ndquadrant.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Pavel Stehule <pavel.stehule@gmail.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Andres Freund <andres@2ndquadrant.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding Tom Lane <tgl@sss.pgh.pa.us>
Re: JSON Function Bike Shedding Robert Haas <robertmhaas@gmail.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Robert Haas <robertmhaas@gmail.com>
Re: JSON Function Bike Shedding "Petr Jelinek" <pjmodos@pjmodos.net>
Re: JSON Function Bike Shedding Josh Berkus <josh@agliodbs.com>
Re: JSON Function Bike Shedding Pavel Stehule <pavel.stehule@gmail.com>
Re: JSON Function Bike Shedding Pavel Stehule <pavel.stehule@gmail.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Robert Haas <robertmhaas@gmail.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Robert Haas <robertmhaas@gmail.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Robert Haas <robertmhaas@gmail.com>
Re: JSON Function Bike Shedding "David E. Wheeler" <david@justatheory.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding Tom Lane <tgl@sss.pgh.pa.us>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding Andrew Dunstan <andrew@dunslane.net>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
Re: JSON Function Bike Shedding Josh Berkus <josh@agliodbs.com>
Re: JSON Function Bike Shedding Merlin Moncure <mmoncure@gmail.com>
On Tue, Feb 12, 2013 at 6:15 PM, Tom Lane wrote: > Josh Berkus writes: >> David, >>> However, I am not so keen on the function names. They all start with >>> json_! This mostly feels redundant to me, since the types of the >>> parameters are part of the function signature. > >> I have no opinion about starting the function names with json_ or not. > > +1 for removing that where possible. We generally have avoided such > names at SQL level. (The C-level function names need such prefixes to > be unique, but the SQL names don't.) > > In the cases where one or more arguments are anyelement, however, we may > need to be more specific to avoid ambiguity problems in future. I agree > with Josh's objections to record(), row() etc. to_record() and > to_recordset() might be OK. ! merlin
В списке pgsql-hackers по дате отправления