27.10.2013 Views

Jaybird 2.1 JDBC driver Java Programmer's Manual - Firebird

Jaybird 2.1 JDBC driver Java Programmer's Manual - Firebird

Jaybird 2.1 JDBC driver Java Programmer's Manual - Firebird

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

commit or rollback and eventually release the resource. More information on<br />

transaction locking modes can be found in Chapter 6, Using transactions.<br />

335544345L isc_lock_conflict "lock conflict on no wait<br />

transaction"<br />

This error happens when a “no wait”<br />

transaction needs to acquire a lock but<br />

finds another concurrent transaction<br />

holding a lock.<br />

Instead of waiting the predefined timeout<br />

hoping that concurrent transaction will<br />

either commit or rollback, an error is<br />

returned to notify an application about the<br />

situation.<br />

335544510L isc_lock_timeout "lock time-out on wait<br />

transaction"<br />

335544336L isc_deadlock "deadlock"<br />

Similar to the isc_deadlock, but is<br />

returned when the lock timeout that was<br />

specified for the current transaction expired<br />

while waiting for a lock.<br />

Another source of this error are DDL<br />

operations that try to obtain a lock on a<br />

database object that is currently used in<br />

some other place.<br />

Two transactions experience a deadlock<br />

when each of them has a lock on a<br />

resource on which another one is trying to<br />

obtain a lock.<br />

Referential Integrity Errors<br />

Referential integrity constrains ensure that database remains in a consistent state<br />

after the DML operation and/or whole transaction is completed. Three primary<br />

error codes are returned when the defined constraints are violated. The error<br />

messages are self-explanatory.<br />

335544665L isc_unique_key_viola<br />

tion<br />

violation of PRIMARY or UNIQUE<br />

KEY constraint "{0}" on table<br />

"{1}"<br />

335544558L isc_check_constraint Operation violates CHECK<br />

constraint {0} on view or table<br />

{1}<br />

335544466L isc_foreign_key violation of FOREIGN KEY<br />

constraint "{0}" on table "{1}"<br />

DSQL Errors<br />

This group contains secondary codes for the primary error code isc_dsql_error<br />

(335544569L), that has a message "Dynamic SQL Error".<br />

335544573L isc_dsql_datatype_err "Data type unknown"<br />

Usually this error is reported during DDL<br />

operation when the specified data type is<br />

either unknown or cannot be used in the<br />

specified statement. However it also can<br />

happen in DML operation, e.g. when an<br />

ORDER BY clause contains unknown<br />

Chapter 3. Handling exceptions 29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!