Error Handling

 

Utilizing exceptions does an error handling. In the case of error Sequel generates an exception with message identifying and describing the error. See below for more details. You will probably see most of them only in crisis situations, i.e. they are provided to get the complete listing of all possible errors and failures.

Error message Meaning
Tables method failed! Enumeration of tables couldn't be invoked.
Columns method failed! Enumeration of columns couldn't be invoked.
Statistics method failed! Enumeration of statistics data couldn't be invoked. ODBC driver does not support this probably.
Table Name may not be an empty string. The name of a table may not be the empty string.
PrimaryKeys method failed! Enumeration of primary keys couldn't be invoked. ODBC driver does not support this probably.
ForeignKeys method failed! Enumeration of foreign key data couldn't be invoked. ODBC driver does not support this probably.
Result set description couldn't be done! Couldn't get any information about the result set.
Can not create a statement! An object implementing IStatement interface couldn't be created. The IDataSource is not connected or it is either possible ODBC error or there is some policy restriction. Refer to your database driver manual.
Bind of result set column failed! Sequel was unable to prepare the access to a result set.
Get data from result set failed Sequel was unable to read from a result set.
Entered SQL statement couldn't be prepared for execution! You've entered statement with invalid syntax or you've used some unsupported feature. In this case refer to your database manual for details about SQL statements.
Execution of SQL statement has failed! ODBC driver didn't execute the statement successfully. E.g. erasing content of non-existing table can invoke this error.
Result set data can not be modified! You have tried to modify values in a result set.
Must be a parameter type, not ResultSet. Data objects in a result set may not be changed into the parameters,
Bind of command parameter has failed! Sequel was unable to prepare execution of SQL statements with parameters. You should check the syntax of the statement.
Couldn't get info about parameters! Sequel was unable to get any information about parameters in the prepared statement.
Entered index is out of bounds. You attempted to read data object with index out of valid bounds of parameters.
Can not disconnect from the data source! An ODBC driver refused your demand for your disconnection from a data source. Probably, there is an active transaction in the manual commit mode.
Can not allocate connection handle! A connection to the specified data source can not be established.
Can not set connection attributes! Sequel was unable to set demanded parameters for the connection.
Can not get info about native data type! Sequel was unable to get info about database supported data types. It is either possible ODBC error or there is some policy restriction. Refer to your database driver manual.
Can not send binary data to data source! Sequel was not unable to send binary data to the ODBC driver.
You have run out of licensed parameters. You have tried to overcome the count of licensed parameters.
Can not get requested information about data source. Sequel was unable to retrieve information needed for the completion of a called method.
Can not change the commit mode! Sequel was unable to change the commit mode between auto and   manual.
Can not end the transaction. The transaction couldn't be successfully committed or rolled back.
Can not change the transaction isolation level! Sequel was unable to change transaction isolation level for the current connection. Check the capabilities of your ODBC driver if it supports requested level. Some drivers require canceling any statement, even if a statement is done.
Can not get the transaction isolation level! Sequel was unable to get the level of the transaction isolation level. Your ODBC driver probably doesn't support transactions.
Can not change the access mode when connected. You've tried to change access mode between read/write and read-only when you were connected to a data source.