| |
| |
The Transaction A transaction is a group of SQL statements whose effects are logically connected. Anything from simple queries to inserting, and deleting operations can be considered a transaction, as well as more complex groups of several statements which accomplish a specific task. Recordset A recordset is the result of executing an SQL query A query is a SQL command that will extract information from the tables of a database. Essentially, a query is a request for information from your database.. It is composed of multiple rows, each row having multiple columns. The columns presented in the query result depend on the column list declared in the query (they can belong to different tables). The number of rows and their order depend on the query conditions (WHERE, GROUP BY, HAVING, ORDER). The recordset acts as a source of dynamic data The InterAKT Dynamic Data tool is a replacement for the standard dynamic data dialog. It is used in the MX Kollection 3, to provide a unified way of building mark-ups, or place holders. These are recordset fields, server or session variables, and other types of dynamic data that are replaced at runtime by their corresponding values in web applications., like regular recordsets, appears in both the Bindings and Server Behaviors tabs of the Application panel.
The Bindings tab will show the collection of all columns referred in all the transactions from the current page.
The Server Behaviors tab will show the recordset as a normal server behavior. There will be some differences as the user will not be able to delete or edit this recordset. Instead it will be pointed to delete or edit the transaction it is related to, as the recordset has no meaning by itself.
When a transaction will be edited, the recordset will be affected as follows:
If there is a change in the transaction column list, the Bindings tab's content will be updated.
If the transaction table is changed:
· If there is another transaction for the same table then nothing will be inserted into the page (in addition to the transaction code changes), but it may have an impact on the Bindings tab as the number of columns may change.
· If there is no transaction for the same table then a new Get the Transaction Recordset code will be inserted into the page for that table.
Deleting the transaction will also affect the recordset:
If there is not another transaction for the same table, the recordset will be removed.
If there is another transaction for the same table, the Binding tab will present a new set of columns as their number may change.