Re: the case for machine-readable error fields - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: the case for machine-readable error fields
Date
Msg-id 1249432569.6126.0.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: the case for machine-readable error fields  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: the case for machine-readable error fields  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
> So, we are just trying to whip into shape explain diagnostics which are 
> in JSON or XML, and now you want us to exclude XML from this one because 
> you don't like it? Can we please try for some consistency?
> 
> Sorry to break it to you, but there are plenty of people and businesses 
> who want XML. And I certainly don't want to have to master every data 
> representation model out there. XML has far more traction than anything 
> else that's comparable in my experience.
> 
> The fact that Greg is prepared to suggest CSV, with its obvious serious 
> deficiencies, as being *better* than XML, makes his whole argument 
> highly suspect IMNSHO.

>From a business perspective, XML is the only viable option for output. 

Joshua D. Drake

-- 
PostgreSQL - XMPP: jdrake@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: the case for machine-readable error fields
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] DefaultACLs