|
|
|
|
|||
|
|
METHOD: |
|
|||
|
|
commit |
|
|||
|
|
|
|
|||
|
|
DESCRIPTION: |
|
|||
|
|
Commits changes made during transaction; ends transaction |
||||
|
|
|
|
|||
|
|
PROPERTY OF: |
|
|||
|
|
|
||||
|
|
|
||||
|
|
SYNTAX: |
|
|||
|
|
<oRef>.commit() |
|
|||
|
|
<oRef> |
The database whose changes you want to commit. |
|||
|
|
|
||||
|
|
DESCRIPTION: |
|
|||
|
|
Calling commit() method saves changes made within an open transaction on the connection and ends the transaction. |
||||
|
|
Affects only the most recently opened transaction; you must close or roll back the current transaction before you can resolve any higher-level transactions. |
||||
|
|
|
||||
|
|
Some database providers, for example Microsoft SQL Server, by default closes an open server cursor when a transaction is committed or rolled back. |
||||
|
|
If given provider supports the preserving cursors (in other words, not closing them after end of transaction) |
||||
|
|
you will can set the "Preserve on Commit" and "Preserve on Abort" dynamic properties for data objects that contains the result rows. |
||||
|
|
In other case you will need re-execution the query or stored procedure for regenerating the rowset. |
||||
|
|
The ADO data objects will be try to regenerate own rowset if is needed to keep the open state of rowset. |
||||
|
|
For better performance of transaction process the preserving cursors is recomended. |
||||
|
|
The "Preserve on Commit" and "Preserve on Abort" properties need to be set prior to opening the data object, for server side-cursor. |
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
|||||
|
|
|||||
|
|
|
|
|||