NNAAMMEE DbException - Exception class for Db activity SSYYNNOOPPSSIISS ##iinncclluuddee <> DDbbEExxcceeppttiioonn::::DDbbEExxcceeppttiioonn((iinntt eerrrr));; DDbbEExxcceeppttiioonn::::DDbbEExxcceeppttiioonn((ccoonnsstt cchhaarr **ddeessccrriippttiioonn));; DDbbEExxcceeppttiioonn::::DDbbEExxcceeppttiioonn((ccoonnsstt cchhaarr **pprreeffiixx,, iinntt eerrrr));; DDbbEExxcceeppttiioonn::::DDbbEExxcceeppttiioonn((ccoonnsstt cchhaarr **pprreeffiixx11,, ccoonnsstt cchhaarr **pprreeffiixx22,, iinntt eerrrr));; ccoonnsstt iinntt DDbbEExxcceeppttiioonn::::ggeett__eerrrrnnoo(());; vviirrttuuaall ccoonnsstt cchhaarr ** DDbbEExxcceeppttiioonn::::wwhhaatt(()) ccoonnsstt;; DDEESSCCRRIIPPTTIIOONN The DB library is a family of classes that provides a mod- ular programming interface to transactions and record-ori- ented file access. The library includes support for transactions, locking, logging and file page caching, as well as various indexed access methods. Many of the classes (e.g., the file page caching class) are useful independent of the other DB classes, although some classes are explicitly based on other classes (e.g., transactions and logging). For a general description of the DB pack- age, see _d_b___i_n_t_r_o(3). This manual page describes the DbException class and how it is used by the various Db* classes. Most methods in the Db classes return an int but also throw an exception. This allows for two different error behaviors, that are known as _e_r_r_o_r _m_o_d_e_l_s. By default, the error model is configured to throw an exception when- ever a serious error occurs. This generally allows for cleaner logic for transaction processing, as a try block can surround a single transaction. Alternatively, the error model can be set to not throw exceptions, and instead request the individual function to return an error code. The error model can be changed using the _D_b_E_n_v_:_:_s_e_t___e_r_r_o_r___m_o_d_e_l method, see _D_b_E_n_v(3). A DbException object contains an informational string and an errno. The errno can be obtained using _D_b_E_x_c_e_p_- _t_i_o_n_:_:_g_e_t___e_r_r_n_o(). The informational string can be obtained using _D_b_E_x_c_e_p_t_i_o_n_:_:_w_h_a_t(). We expect in the future that this class will inherit from the standard class exception, but certain language imple- mentation bugs currently prevent this on some platforms. Some methods may return non-zero values without issuing an exception. This occurs in situations that are not nor- mally considered an error, but when some informational status is returned. For example, _D_b_:_:_g_e_t returns DB_KEYNOTFOUND when a requested key does not appear in the database. SSEEEE AALLSSOO _d_b___a_r_c_h_i_v_e(1), _d_b___c_h_e_c_k_p_o_i_n_t(1), _d_b___d_e_a_d_l_o_c_k(1), _d_b___d_u_m_p(1), _d_b___l_o_a_d(1), _d_b___r_e_c_o_v_e_r(1), _d_b___s_t_a_t(1), _d_b___i_n_t_r_o(3), _d_b___i_n_t_e_r_n_a_l(3), _d_b___t_h_r_e_a_d(3), _D_b(3), _D_b_c(3), _D_b_E_n_v(3), _D_b_E_x_c_e_p_t_i_o_n(3), _D_b_I_n_f_o(3), _D_b_L_o_c_k(3), _D_b_L_o_c_k_T_a_b(3), _D_b_L_o_g(3), _D_b_L_s_n(3), _D_b_M_p_o_o_l(3), _D_b_M_p_o_o_l_F_i_l_e(3), _D_b_t(3), _D_b_T_x_n(3), _D_b_T_x_n_M_g_r(3)