| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | <pgsql-jdbc(at)postgresql(dot)org> |
| Cc: | <pgsql-patches(at)postgresql(dot)org> |
| Subject: | SQLState implementation for V3 Protocol |
| Date: | 2003-09-08 12:17:52 |
| Message-ID: | Pine.LNX.4.33.0309080812540.10757-300000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-patches |
I've added parsing of the V3 protocol's notice and error messages into its
various fields. This replaces the current error message format of:
SERRORC42P01Mrelation "this_table_doesnt_exist" does not
existFnamespace.cL193RRangeVarGetRelid
with the correct message and allows the programmer to retrieve the
SQLState via the standard getSQLState call.
One thing that I am concerned about is that the message fields are
separated by null bytes, but what happens when we are using an encoding
that allows embedded nulls?
Kris Jurka
| Attachment | Content-Type | Size |
|---|---|---|
| sqlstate.diff | text/plain | 7.0 KB |
| PGErrorMessage.java | text/plain | 3.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zak McGregor | 2003-09-08 13:25:47 | Resultset funnies... |
| Previous Message | Michael Stephenson | 2003-09-08 09:10:03 | Re: expression IN value list |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2003-09-08 13:32:59 | Re: mcxt.c |
| Previous Message | Manfred Koizar | 2003-09-08 11:27:28 | Re: [HACKERS] Index creation takes for ever |