Skip site navigation (1) Skip section navigation (2)

Error codes revisited

From: greg(at)turnstep(dot)com
To: pgsql-hackers(at)postgresql(dot)org
Subject: Error codes revisited
Date: 2003-03-04 20:24:08
Message-ID: 3c8f53ba842274dde1ce2c07c063f265@biglumber.com (view raw or flat)
Thread:
Lists: 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(at)turnstep(dot)com
PGP Key: 0x14964AC8 200303041516

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+ZQo2vJuQZxSWSsgRAiKiAKDImuVDD5v4mvY1ClrTo9YrYFlDogCgwz1C
Q/DS7rHZ2XWCPuZd8oQoVeA=
=ixmb
-----END PGP SIGNATURE-----


Responses

pgsql-hackers by date

Next:From: Eric D NielsenDate: 2003-03-04 20:26:37
Subject: Updateable views...
Previous:From: gregDate: 2003-03-04 19:50:12
Subject: Re: XML ouput for psql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group