Programming Guide |
Fetches the last set of rows from the file
int sm_tm_command ("CONTINUE_BOTTOM [tableViewName
[tableViewScope
] ]");
tableViewName
- The name of a table view in the current transaction. This parameter is case sensitive. If
tableViewName
is specified, the command is applied according to thetableViewScope
parameter. Since the entire table view tree might not be included, this is known as a partial command, andsm_tm_command
setsTM_FULL
to 0.If
tableViewName
is not specified, the command is applied for each table/server view, starting with the root table view. This is known as a full command, andsm_tm_command
setsTM_FULL
to 1.tableViewScope
- One of the following parameters, which must be preceded by a table view name.
TV_AND_BELOW
which applies the command to the specified table view and all table views below it on the tree. If no parameter is specified, the transaction manager acts as thoughTV_AND_BELOW
was supplied.
BELOW_TV
which applies the command to the table views below the specified table view.
TV_ONLY
which applies the command to the specified table view only.
SV_ONLY
which applies the command only to the table views of the specified server view.
CONTINUE_BOTTOM
(not available in Web applications or three-tier processing) fetches the last set of rows from the file. The availability of this command is de pendent on the setting of thefetch_directions
property for the server view or screen. If thefetch_directions
property is set toPV_CONT_ALWAYS
(Up/ Down-all modes), this command is available in update or view mode. If thefetch_directions
property is set toPV_CONT_VIEW_ONLY
(Up/Down-view mode), this command is available only in view mode. Otherwise, an error is generated. For more information on setting the Fetch Directions property, refer to "Scrolling Through the Select Set" in Application Development Guide.If your screen has multiple table views, the transaction manager issues a
DBMS
CONTINUE_BOTTOM
for the specified table view and any table views linked to it via server links. This displays the last set of rows for that server view. ThenSELECT
orVIEW
processing is done for any additional child table views.The data displayed with this command is from a continuation file; it is not refetched from the database. Therefore, any updates made to the data in this server view are not displayed immediately to other users. In order to display those updates, the data must be refetched from the database with a
VIEW
orSELECT
command.The advantage of using the continuation file is that it prevents having shared locks on data. However, if the
fetch_directions
property is set toPV_CONT_ALWAYS
(Up/Down-all modes), you are responsible for implementing the necessary locking scheme for concurrent users. For more information on using the Version Column property to implement optimistic locking, refer to "Implementing Optimistic Locking" in Application Development Guide.If you want to use the database engine's facilities for non-sequential scrolling, you need to add processing for the request events to the engine-specific transaction model.
Push buttons and menu selections for the
CONTINUE_BOTTOM
command can choose to set the class property tocontinue_button
which activates the option only in view and update modes or tocontinue_view_button
which activates the option only in view mode.
Use
CONTINUE_BOTTOM
afterSELECT
orVIEW
which generate a database query and display the first set of query results or after any otherCONTINUE
command.
The following requests can be generated by the
CONTINUE_BOTTOM
command to ascertain if the changes from the previous command have been saved and, if desired, to discard those changes:
TM_PRE_CLOSE
(described underCLOSE
)
TM_CLOSE
(described underCLOSE
)
TM_QUERY
(described underCLOSE
)
The following requests can also be generated for any child table views:
TM_PRE_SELECT
(described underSELECT
)
TM_SELECT
(described underSELECT
)
TM_POST_SELECT
(described underSELECT
)
TM_PRE_VIEW
(described underVIEW
)
If
TM_VIEW
orTM_SELECT
for a parent table view returns no data,TM_CLEAR
requests are generated for all subordinate table views, but not for table views at the same level of the tree.TM_CLEAR
requests are described underCLEAR
.