| From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Practical sets of SQLSTATE values? |
| Date: | 2003-05-30 16:06:58 |
| Message-ID: | Pine.BSF.4.44.0305301204470.66728-100000@torgo.978.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 30 May 2003, Tom Lane wrote:
> What do other DBMSes do about this? Seems like it would make sense to
> borrow as many SQLSTATE codes as we can from Oracle or DB2 or some other
> big player ... especially if there's any commonality in their
> extensions. Anyone have lists of implementation-defined SQLSTATEs for
> the big commercial DBs?
>
On informix SQLSTATE is mostly for getting the oh.. lets call it the
"genre" of the error. They use a separate error code which contains the
specific error.
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-30 17:32:39 | Re: index suggestion for 7.4 |
| Previous Message | Oleg Bartunov | 2003-05-30 16:06:26 | XML and postgres |