ISDBDatabase::ForceCommit: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
===Method description=== | ===Method description=== | ||
Finishes already started SQL transaction. It had to be previously started by [[ISDBDatabase::BeginTransaction|BeginTransaction]]. Unlike ordinary [[ISDBDatabase::Commit]] this method always forces SQL COMMIT command to proceed and thus waits for other threads to finish what they are currently doing. [[ISDBDatabase::Commit]] is a preferred method, use ForceCommit only in case you need to unlock database for some reason. | Finishes already started SQL transaction. It had to be previously started by [[ISDBDatabase::BeginTransaction|BeginTransaction]]. Unlike ordinary [[ISDBDatabase::Commit|Commit]] this method always forces SQL COMMIT command to proceed and thus waits for other threads to finish what they are currently doing. [[ISDBDatabase::Commit|Commit]] is a preferred method, use ForceCommit only in case you need to unlock database for some reason. | ||
Introduced in MediaMonkey 3.0.3.1179. | Introduced in MediaMonkey 3.0.3.1179. | ||
Revision as of 21:45, 27 May 2008
CoClass SDBDatabase, Interface ISDBDatabase
Sub ForceCommit
Method description
Finishes already started SQL transaction. It had to be previously started by BeginTransaction. Unlike ordinary Commit this method always forces SQL COMMIT command to proceed and thus waits for other threads to finish what they are currently doing. Commit is a preferred method, use ForceCommit only in case you need to unlock database for some reason.
Introduced in MediaMonkey 3.0.3.1179.
