FBSQLException contains least specific errorcode [JDBC221] #270
Assignees
Comments
|
Commented by: @mrotteveel It looks like this has changed in Firebird 3.0 (or at least I saw that a DROP table (if the table does not exist) which in FB 2.5 throws a isc_dsql_error first, now returns the more specific isc_no_meta_update) |
Modified by: @mrotteveelassignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ] |
Modified by: @mrotteveelFix Version: Jaybird 3.0 [ 10440 ] |
|
Commented by: @mrotteveel Added heuristics when creating exceptions to select a more specific error code and sql state. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @mrotteveel
When attempting to drop a table which does not exist the error code returned by FBSQLException.getErrorCode() is isc_dsql_error = 335544569. The most specific error code however is isc_dsql_table_not_found = 336397206 which is found deep in a chain of GDSException.next.
I would think that returning the most specific error would be more helpful.
Commits: 56d54e9 909611c FirebirdSQL/fbt-repository@86db8b5
The text was updated successfully, but these errors were encountered: