To commit changes and continue with your editing session, use the primary command
SAVE. This commits changes without exiting the current session. To commit changes and exit to the workbench, press PF3.
The Table Editor displays a message at the bottom of the screen to indicate whether the changes are committed. For example, you see a message similar to:
Updates to table ”EMPLOYEE(NORTHWEST)” saved. When changes are committed, they are saved in the ascending order of the primary key.
When changes are not committed, a message at the bottom of the display screen gives a reason for the failure and the Table Editor positions the cursor where corrections are required.
To commit changes to an occurrence, press PF3 or use the primary command SAVE. In either case, the new occurrence or the updates to an existing occurrence are committed, the table is updated, and the editing session is terminated.
At the end of every transaction, TIBCO Object Service Broker implicitly commits changes to the database made since the last synchronization point. Synchronization points can be established using the COMMIT and ROLLBACK statements from within a rule.
Do not modify the definitions of those two fields, which must always remain as the last two fields in the table definition. If they are absent, Object Service Broker rejects access to the EES table.
Because EES tables can be shared in a multiuser Execution Environment, although their processing is similar to that of SES and TEM tables, some changes are necessary to maintain data integrity. Read on for the details.
For a nonupdate processing to an EES table, Object Service Broker obtains a shared global lock for all the EES tables for the duration of the request. Whenever a row in the table is referenced by a nonupdate request, Object Service Broker increments the field
@@REF_COUNT by 1.
For an update processing to an EES table, Object Service Broker obtains an exclusive global lock for all the EES tables for the duration of the update request. That is, once control is to return to the processing rule, Object Service Broker releases the lock.
To replace a row in a table, if the field @@UPDATE_COUNT exists in the replacement buffer, Object Service Broker compares it with the value in the actual table data. Depending on the result, either of the following occurs:
If the field @@UPDATE_COUNT does not exist in the replacement buffer, Object Service Broker replaces the row in the actual table data and increments the fields
@UPDATE_COUNT and
@@REF_COUNT by 1.
To delete a row in a table, if the field @@UPDATE_COUNT exists in the deletion buffer, Object Service Broker compares it with the value in the actual table data. Depending on the result, either of the following occurs:
If the field @@UPDATE_COUNT does not exist in the row buffer, Object Service Broker deletes the row.
Consider two transactions, A and B, both of which are attempting to update row X in an EES table. Assume that row X is currently in its initially inserted state, that is, fields
@@REF_COUNT and
@@UPDATE_COUNT are set to 1.
TIBCO Object Service Broker Programming in Rules for information on the COMMIT and ROLLBACK statements and synchronization of the database.