. . . 25 14. Error Handling And Exception Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 15. Transaction Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 16. Script Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . You should be aware that unless you also pass the username and password as well, you may see an error message telling you that your username or password have not been defined. In this case, you need

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.1.3. Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 7.7. Trapping and Handling Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 SQLSTATE Error Codes and Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 SQLCODE and GDSCODE Error Codes and Descriptions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.1.3. Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 7.8. Trapping and Handling Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 8.12.2. RDB$ERROR(). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

to API DPB Parameters in V.2.1.2 and V.2.0.5: IMPORTANT A long-standing, legacy loophole in the handling of DPB parameters enabled ordinary users to make con- nection settings that could lead to database CHECK Constraint Change Formerly, CHECK constraints were not SQL standard-compliant in regard to the handling of NULL. For example, CHECK (DEPTNO IN (10, 20, 30)) should allow NULL in the DEPTNO column but RDB$RELATIONS.RDB$RELATION_NAME FROM RDB$RELATIONS R Now, the engine will correctly report an error that the field “RDB$RELATIONS.RDB $RELATION_NAME” could not be found. Use this (preferred): SELECT

following: • Command line options for the gfix database utility. • Shadow file handling. • Cache and buffer handling. • Transaction management. • Cache management. • Starting and stopping a database failed, SQLCODE = -901 lock conflict on no wait transaction -I/O error for file "/home/norman/firebird/shadow/my_employee.shd2" -Error while trying to open file -No such file or directory -a file in manual transaction in database my_employee transaction is not in limbo -transaction 388 is active unknown ISC error 0 When committing or rolling back all limbo transactions, the -⁠pr[ompt] option can be specified

(hence the Shared). • Superserver (ThreadedDedicated) is also a single server process with threads handling client connections. There is a single, common database page cache. The server requires exclusive database without credentials (and making sure no embedded connection is made) will result in this error message: SQL> connect xnet://employee; Statement failed, SQLSTATE = 28000 Missing security context should use these with caution, as it’s not always obvious how they will be expanded. Getting an error message is annoying enough, but applying changes to another database than you thought you were connected

of the functions listed above under Firebird 2, and you want to benefit from the improved NULL handling, run the script ib_udf_upgrade.sql Chapter 13. User-Defined Functions (UDFs) 39 against your NULL can be treated in the same way as some allowed value for the datatype. If NULL needs special handling, different from any other value, your only option is to use an IF or CASE construct after all. Alphabetical index 1.0. 1 26 Jan 2007 PV Making non-nullable columns nullable again: Provisory fix of error regarding removal of NOT NULL constraints. Appendix B: Document history 63 Revision History 1

cannot therefore reuse any allocated RDB$GENERATOR_ID, it is not surprising that the simplest way of handling a dropped sequence is simply to ignore it. If you are creating and dropping sequences frequently

Firebird 2.1 Error Codes Firebird 2.1 Error Codes SQLCODE GDSCODE SYMBOL TEXT 101 335544366 segment Segment buffer length shorter than expected 101 335544366 segment Segment buffer length shorter than the security database -85 335544754 error_adding_sec_record An error occurred while attempting to add the user. -85 335544755 error_modifying_sec_record An error occurred while attempting to modify the 335544756 error_deleting_sec_record An error occurred while attempting to delete the user record. -85 335544757 error_updating_sec_db An error occurred while updating the security Firebird 2.1 Error Codes

Firebird 2.0 Error Codes Firebird 2.0 Error Codes SQLCODE GDSCODE SYMBOL TEXT 101 335544366 segment Segment buffer length shorter than expected 100 335544338 from_no_match No match for first value the security database -85 335544754 error_adding_sec_record An error occurred while attempting to add the user. -85 335544755 error_modifying_sec_record An error occurred while attempting to modify the the user record. -85 335544756 error_deleting_sec_record An error occurred while attempting to delete the user record. -85 335544757 error_updating_sec_db An error occurred while updating the security