Re: ambiguous sql states
От | Dave Cramer |
---|---|
Тема | Re: ambiguous sql states |
Дата | |
Msg-id | 1061759677.2211.122.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: ambiguous sql states (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Tom, The reason it is of importance to me/ecpg is for informix compatibility. informix returns a unique errorcode for the copy operation when the file is not found. this isn't much of an argument from a postgres POV, however I still find the sqlstate to be ambiguous. Dave On Sun, 2003-08-24 at 16:46, Tom Lane wrote: > Peter Eisentraut <peter_e@gmx.net> writes: > > Dave Cramer writes: > >> I'm working on identifying various errors in ecpg using sql state and > >> one which is particularly ambiguous is ERRCODE_UNDEFINED_OBJECT for a > >> file which isn't found. This is returned in a number of places. Is it > >> possible to get a set of file specific error codes? > > > That error code if for undefined objects, not files that can't be found. > > Dave's correct, that's what we're currently using. I'm happy to change > it if someone can suggest an appropriate SQLSTATE (even a category...) > to use instead. > > I would however like to know why ecpg cares. > > regards, tom lane > -- Dave Cramer <dave@fastcrypt.com> fastcrypt
В списке pgsql-hackers по дате отправления: