|
|
|
|
Errors raised by the SQL queries are handled in compliance with the error reporting mode selected at design time from the InterAKT Control Panel: production or development.
There are two types of SQL errors:
Field errors - these errors are directly related to a particular field which caused them. A message is displayed next to the form field that caused it.
General errors - these errors have a more general cause (e.g. the database server cannot be contacted, etc), and are displayed on top of the page.
When in production mode, only a limited amount of information regarding
the SQL transaction
and field that failed is displayed, as shown in the image below, where
a SQL error was raised due to an attempt to add a null value into a non-null
field.
As you can see, the error message is clear and concise, pointing to the wrong entry, as well as hiding complex detail.
When switching to development mode for error reporting, a detailed trace
of all transactions and triggers until the error is displayed, along with
detailed information on the exact query
that failed and the reason why it did. Also, a link to explain possible
causes and solutions is provided. The same error as above is now completely
explained, pointing the developer to the exact line of code that caused
the error. This way it is easier to identify programming errors versus
bad input errors.
The first zone displays the same error message as for production mode.
The second one, marked developer details, shows the exact query, filled with the values that it was trying to process, that failed.
The Transaction Engine 3 Execution Trace
is not expanded at first, but it can be made fully visible by clicking
the View link.