| From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, <neilc(at)samurai(dot)com>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Implementation of SQLCODE and SQLERRM |
| Date: | 2005-04-19 06:09:24 |
| Message-ID: | Pine.LNX.4.44.0504190748050.32594-100000@kix.fsv.cvut.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Tue, 19 Apr 2005, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Guys, is this patch ready for application? I think so, but am not 100%
> > sure.
>
> I haven't read the code yet, but in any case I still object to choosing
> Oracle-like names for Oracle-incompatible functionality. We need to
> settle on better names.
>
I changed names on SQLSTATE and SQLERRM. The behave our SQLSTATE and db2
SQLSTATE is very similar. But Oracle support SQLSTATE too (in ANSI mode).
Only Oracle support SQLERRM.
http://developer.mimer.com/howto/howto_25.htm
SQLSTATE, a 5-character return value specified by the SQL standard,
replaced SQLCODE years ago (SQL-92?). Perhaps both Oracle and DB2/2
have support for it.
But I didn't find good informations about error trapping in ANSI SQL. All
informations are about Oracle or DB2 :-(.
Best Regards
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-04-19 06:17:32 | Re: Weirdess when altering serial column type |
| Previous Message | Tom Lane | 2005-04-19 06:07:02 | Re: Weirdess when altering serial column type |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2005-04-19 13:41:38 | Implementation of SQLSTATE and SQLERRM variables |
| Previous Message | Pavel Stehule | 2005-04-19 05:00:20 | Re: [HACKERS] Implementation of SQLCODE and SQLERRM |