Hello folks:
I am using DBI to connect to a postgreSQL database and thought it
would be a good idea to anticipate and handle errors returned by
postgreSQL in my perl code so the end user doesn't have to deal with
mysterious error messages he can't understand. "Programming the Perl
DBI" suggests using $h->errstr() but says that the message is determined
by the underlying database.
I've checked a couple of PostgreSQL books and the online docs as well
as the web but haven't found any kind of list of the possibilities. It
would seem that if it were useful to know them someone would have
documented it, so I am wondering if I am just approaching the problem of
error messages the wrong way. Yet I don't see how you can deal with
errors unless you know what the errors can possibly be, short of trying
to make force every error possible and looking at the resulting string.
Can anyone suggest a different approach ?
Thanks
--
Bill Kurland
Shakespeare & Co.
"There is no Modesty--No attention to one another. They talk very loud,
very fast,and alltogether.If they ask you a Question, before you can
utter 3 words of your Answer, they will break out upon you, again--and
talk away"
--John Adams, on New Yorkers
- Re: PostgreSQL error strings - a list Bill Kurland
- Re: PostgreSQL error strings - a list David Wheeler
- Re: PostgreSQL error strings - a list Wil Peters
