From 8b4e42208321d0f9eff192bf4e5eef580652c10b Mon Sep 17 00:00:00 2001 From: zYne Date: Fri, 20 Jul 2007 19:31:17 +0000 Subject: [PATCH] --- tests/Search/_files/content.html | 7 +++++++ tests/Search/_files/content.txt | 12 ++++++++++++ 2 files changed, 19 insertions(+) create mode 100644 tests/Search/_files/content.html create mode 100644 tests/Search/_files/content.txt diff --git a/tests/Search/_files/content.html b/tests/Search/_files/content.html new file mode 100644 index 000000000..e5461086a --- /dev/null +++ b/tests/Search/_files/content.html @@ -0,0 +1,7 @@ +Database transaction +From Wikipedia, the free encyclopedia +Jump to: navigation, search +A database transaction is a unit of interaction with a database management system or similar system that is treated in a coherent and reliable way independent of other transactions that must be either entirely completed or aborted. Ideally, a database system will guarantee the properties of Atomicity, Consistency, Isolation and Durability (ACID) for each transaction. In practice, these properties are often relaxed somewhat to provide better performance. + +In some systems, transactions are also called LUWs for Logical Units of Work. + diff --git a/tests/Search/_files/content.txt b/tests/Search/_files/content.txt new file mode 100644 index 000000000..af807786f --- /dev/null +++ b/tests/Search/_files/content.txt @@ -0,0 +1,12 @@ +This file contains only contains some plain text copied from wikipedia. + +In database products the ability to handle transactions allows the user to ensure that integrity of a database is maintained. + +A single transaction might require several queries, each reading and/or writing information in the database. When this happens it is usually important to be sure that the database is not left with only some of the queries carried out. For example, when doing a money transfer, if the money was debited from one account, it is important that it also be credited to the depositing account. Also, transactions should not interfere with each other. For more information about desirable transaction properties, see ACID. + +A simple transaction is usually issued to the database system in a language like SQL in this form: + +Begin the transaction +Execute several queries (although any updates to the database aren't actually visible to the outside world yet) +Commit the transaction (updates become visible if the transaction is successful) +If one of the queries fails the database system may rollback either the entire transaction or just the failed query. This behaviour is dependent on the DBMS in use and how it is set up. The transaction can also be rolled back manually at any time before the commit.