Fabien COELHO <coe...@cri.ensmp.fr> writes:
>> * It might be better if SQLSTATE and ERROR_MESSAGE were left
>> unchanged by a non-error query.
> Hmmm. I'm not sure. If so, ERROR_MESSAGE should be LAST_ERROR_MESSAGE
> maybe? Then what about LAST_ERROR_SQLSTATE to go with it, and let SQLSTATE
> & ERROR_MESSAGE reflect the last command, and ERROR is just the boolean to
> test if it occured?
>> That would reduce the need to copy them into other variables just
>> because you needed to do something else before printing them. It'd save
>> a few cycles too.
> Well, my suggestion would mean that they would be copied when an error
> occurs, but only when it occurs, which would not be often.
Uh ... what?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
