🚀 go-pugleaf

AJ,

SQLException.getSQLState() returns a "SQLstate string, which follows the
XOPEN SQLstate conventions".
SQLException.getErrorCode() returns "the vendor-specific exception code".

If it's only about the update/insert problem I suggest you do a simple
"select count(*)" to check if the row is already there or not.

Torsten

AJ schrieb in Nachricht <3aad0fc8$1_2@dnews>...
>After a call to PreparedStatement.executeUpdate to do an insert, I get an
>SQLException.  How do I determine if this is due to a duplicate key, i.e.
>the row is already there?  Are there sub-types to SQLExceptions?  Do I have
>to look at XOPEN SQL states?  I need this to be database independent, so
>vendor-specific error codes will not help.
>
>Bottom line:  if the row is duplicate, I want to update instead of insert.
>I suppose I could just try to update if the insert fails, but I'd like to
be
>sure that I'm only doing so in the specific case of a duplicate row error.
>
>Thanks,
>AJ
>
>
>