Re: [PATCH] Generalized JSON output functions

2015-07-16 19:51 GMT+02:00 Robert Haas <robertmhaas(at)gmail(dot)com>:

> On Wed, Jul 15, 2015 at 1:10 PM, Ryan Pedela <rpedela(at)datalanche(dot)com>
> wrote:
> > Like I said previously, the
> > situation with Javascript will hopefully be remedied in a few years with
> ES7
> > anyway.
>
> I don't understand these issues in great technical depth, but if
> somebody is arguing that it's OK for PostgreSQL to be difficult to use
> for a certain category of user for several years until the next
> language rev becomes mainstream, then I disagree. The fact that
> somebody wrote a patch to try to solve a problem means that the thing
> in question is a problem for at least that one user. If he's the only
> one, maybe we don't need to care all that much. If his needs are
> representative of a significant user community, we should not turn our
> backs on that community, regardless of whether we like the patch he
> wrote, and regardless of how well we are meeting the needs of other
> communities (like node.js users).
>

I don't think so this issue is too hot. How long we support XML? The output
format is static - the date format is fixed. How much issues was there?
Was there any issue, that was not solvable by casting?

If somebody needs different quoting, then it can be solved by explicit cast
in SQL query, and not in hacking our output routines.

Regards

Pavel

> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>