Error codes revisited
От | greg@turnstep.com |
---|---|
Тема | Error codes revisited |
Дата | |
Msg-id | 3c8f53ba842274dde1ce2c07c063f265@biglumber.com обсуждение исходный текст |
Ответы |
Re: Error codes revisited
|
Список | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As promised, I've been looking over the error handling (especially the archived discussions) and it's a real rat's nest. :) I'm not sure where we should start, but just getting some error codes enabled and out there would be a great start. The protocol changes can come later. And the codes should not be part of the string. What about a variable that allowed the codes to be switched on so a number is returned instead of a string? This would be off by default so as not to break existing applications. Similarly, we can return other information (FILE, LINE, etc.) with different variables. This should all be doable without a protocol change, as long as everything is returned as a string in a standard format. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200303041516 -----BEGIN PGP SIGNATURE----- Comment: http://www.turnstep.com/pgp.html iD8DBQE+ZQo2vJuQZxSWSsgRAiKiAKDImuVDD5v4mvY1ClrTo9YrYFlDogCgwz1C Q/DS7rHZ2XWCPuZd8oQoVeA= =ixmb -----END PGP SIGNATURE-----
В списке pgsql-hackers по дате отправления: