Re: the case for machine-readable error fields

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: the case for machine-readable error fields
Дата
Msg-id ad816211acd2c9f3a6397be27397b052@biglumber.com
обсуждение исходный текст
Ответ на Re: the case for machine-readable error fields  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: the case for machine-readable error fields  (David Fetter <david@fetter.org>)
Список pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> If that's what we're trying to solve, I don't think that adding some
> kind of proprietary shorthand coding is a good idea.  If we're do to
> this at all, it should be a connection-based GUC option, and use some
> standard formal like XML fragments.

+1 to this idea in general, but *please* don't consider the use of
XML. If we really need some sort of formatting, let's do CSV. Or
YAML. Or JSON. Anything but XML.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200908041806
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkp4sOoACgkQvJuQZxSWSsjItACgsDtcid8Zqx9J2ehIhqbtN1l3
1jMAoNcd/6eJPBkKbdNYx6wbUl3bnxhC
=H5yv
-----END PGP SIGNATURE-----




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: head contrib is broken (crypto)
Следующее
От: Bernd Helmle
Дата:
Сообщение: Re: mixed, named notation support