Re: [HACKERS] psql - add special variable to reflect the last query status
| От | Tom Lane |
|---|---|
| Тема | Re: [HACKERS] psql - add special variable to reflect the last query status |
| Дата | |
| Msg-id | 7870.1504634891@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: [HACKERS] psql - add special variable to reflect the last querystatus (Fabien COELHO <coelho@cri.ensmp.fr>) |
| Ответы |
Re: [HACKERS] psql - add special variable to reflect the last querystatus
|
| Список | pgsql-hackers |
Fabien COELHO <coelho@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
В списке pgsql-hackers по дате отправления: