KB crawler nightly commit

MariaDB · Oct 4, 2024 · b50ed25 · b50ed25
1 parent 62b9d73
commit b50ed25
Show file tree

Hide file tree

Showing 31 changed files with 376 additions and 933 deletions.
diff --git a/archive/+changes/index.html b/archive/+changes/index.html
diff --git a/archive/en/acid-concurrency-control-with-transactions/+comments/feed/index.html b/archive/en/acid-concurrency-control-with-transactions/+comments/feed/index.html
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: ACID: Concurrency Control with Transactions</title><link>https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Mon, 30 Sep 2024 05:05:48 +0000</lastBuildDate></channel></rss>
+<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: ACID: Concurrency Control with Transactions</title><link>https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Fri, 04 Oct 2024 00:02:31 +0000</lastBuildDate></channel></rss>
diff --git a/archive/en/acid-concurrency-control-with-transactions/+comments/index.html b/archive/en/acid-concurrency-control-with-transactions/+comments/index.html
@@ -31,7 +31,7 @@
 Comments - ACID: Concurrency Control with Transactions
 " />
     <meta property="og:type" content="article" />
-    <meta property="og:url" content="https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments" />
+    <meta property="og:url" content="https://mariadb.com/kb/en/acid-concurrency-control-with-transactions/+comments/" />
     <meta property="og:image" content="http://mariadb.comaskmonty-logo.png" />
     <meta property="og:site_name" content="MariaDB KnowledgeBase" />
     <meta property="fb:admins" content="514852603" />
@@ -76,7 +76,7 @@
                 </li>
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/acid-concurrency-control-with-transactions/+comments"> Login</a>
+                        <a href="/kb/user/login?next=/kb/en/acid-concurrency-control-with-transactions/+comments/"> Login</a>
                     </li>
 
             </ul>
@@ -121,7 +121,7 @@
 
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/acid-concurrency-control-with-transactions/+comments" rel="nofollow">Login</a>
+                        <a href="/kb/user/login?next=/kb/en/acid-concurrency-control-with-transactions/+comments/" rel="nofollow">Login</a>
                     </li>
 
 

diff --git a/archive/en/acid-concurrency-control-with-transactions/+source/index.html b/archive/en/acid-concurrency-control-with-transactions/+source/index.html
@@ -311,7 +311,7 @@ <h1>ACID: Concurrency Control with Transactions - Source</h1>
     <div class="revision_info">
         <dl class="table">
             <dt>Revision</dt>
-            <dd><a href="/kb/en/acid-concurrency-control-with-transactions/+r/71775/">71775</a></dd>
+            <dd><a href="/kb/en/acid-concurrency-control-with-transactions/+r/143750/">143750</a></dd>
             <dt>User</dt>
             <dd>
 <span class="user" id="user-1368">
@@ -320,7 +320,7 @@ <h1>ACID: Concurrency Control with Transactions - Source</h1>
             <dt>Date</dt>
             <dd>
 
-<span class="datetime" title="2018-08-08 08:38">2018-08-08 08:38</span></dd>
+<span class="datetime" title="2024-10-03 10:07">2024-10-03 10:07</span></dd>
         </dl>
     </div>
 
@@ -335,16 +335,16 @@ <h1>ACID: Concurrency Control with Transactions - Source</h1>
 To ensure data integrity, transactions need to adhere to four conditions: atomicity, consistency, isolation and durability (ACID).
 
 === Atomicity
-//Atomicity// means the entire transaction must complete. If this is not the case, the entire transaction is aborted. This ensures that the database can never be left with partially completed transactions, which lead to poor data integrity. If you remove money out of one bank account, for example, but the second request fails and the system cannot place the money in another bank, both requests must fail. The money cannot simply be lost, or taken from one account without going into the other.
+//Atomicity// means the entire transaction must complete. If this is not the case, the entire transaction is aborted. This ensures that the database is never left with partially completed transactions, which would lead to data integrity issues. For example, if money is debited from one bank account but an error occurs before it can be credited to another account, the entire transaction must fail. The money cannot be lost or taken from one account without being successfully deposited into the other.
 
 === Consistency
-//Consistency// refers to the state the data is in when certain conditions are met. For example, one rule may be that each invoice must relate to a customer in the customer table. These rules may be broken during the course of a transaction if, for example the invoice is inserted without a related customer, which is added at a later stage in the transaction. These temporary violations are not visible outside of the transaction, and will always be resolved by the time the transaction is complete.
+//Consistency// ensures that data adheres to predefined rules or constraints. For example, a rule might state that each invoice in the invoices table must be linked to a customer in the customers table. During a transaction, these rules can be temporarily violated—such as inserting an invoice before adding the related customer—but only within the transaction itself. These temporary violations are not visible outside the transaction and are always resolved before the transaction is finalized.
 
 === Isolation
-//Isolation// means that any data being used during the processing of one transaction cannot be used by another transaction until the first transaction is complete. For example, if two people deposit $100 into another account with a balance of $900, the first transaction must add $100 to $900, and the second must add $100 to $1000. If the second transaction reads the $900 before the first transaction has completed, both transactions will seem to succeed, but $100 will have gone missing. The second transaction must wait until it alone is accessing the data.
+//Isolation// ensures that data being used by one transaction is inaccessible to other transactions until the first transaction is complete. For example, if two people deposit $100 each into an account with a balance of $900, the first transaction must update the balance to $1,000, and the second must then update it to $1,100. If the second transaction reads the $900 balance before the first transaction finishes, both transactions will appear successful, but $100 will be lost. The second transaction must wait until the first completes to access the correct balance.
 
 === Durability
-//Durability// refers to the fact that once data from a transaction has been committed, its effects will remain, even after a system failure. While a transaction is under way, the effects are not persistent. If the database crashes, backups will always restore it to a consistent state prior to the transaction commencing. Nothing a transaction does should be able to change this fact.</textarea>
+//Durability// guarantees that once a transaction is committed, its effects are permanent, even in the event of a system failure. While a transaction is in progress, its changes are not yet permanent. If the database crashes before the transaction is committed, the system can be restored to a consistent state using backups, which reflect the state before the transaction started. A committed transaction cannot be undone by a failure.</textarea>
 
 
 

diff --git a/archive/en/acid-concurrency-control-with-transactions/index.html b/archive/en/acid-concurrency-control-with-transactions/index.html
@@ -275,7 +275,7 @@
         <dt>Modified</dt>
         <dd>
 
-<span class="datetime" title="2018-08-08 08:38">6 years, 1 month ago</span></dd>
+<span class="datetime" title="2024-10-03 10:07">13 hours, 55 minutes ago</span></dd>
 
         <dt>Type</dt>
         <dd>article</dd>
@@ -410,13 +410,13 @@ <h1>ACID: Concurrency Control with Transactions</h1>
         <p>Database requests happen in linear fashion, one after another. When many users are accessing a database, or one user has a related set of requests to run, it becomes important to ensure that the results remain consistent. To achieve this, you use <em>transactions</em>, which are groups of database requests that are processed as a whole. Put another way, they are logical units of work.</p>
 <p>To ensure data integrity, transactions need to adhere to four conditions: atomicity, consistency, isolation and durability (ACID).</p>
 <h3 class="anchored_heading" id="atomicity">Atomicity</h3>
-<p><em>Atomicity</em> means the entire transaction must complete. If this is not the case, the entire transaction is aborted. This ensures that the database can never be left with partially completed transactions, which lead to poor data integrity. If you remove money out of one bank account, for example, but the second request fails and the system cannot place the money in another bank, both requests must fail. The money cannot simply be lost, or taken from one account without going into the other.</p>
+<p><em>Atomicity</em> means the entire transaction must complete. If this is not the case, the entire transaction is aborted. This ensures that the database is never left with partially completed transactions, which would lead to data integrity issues. For example, if money is debited from one bank account but an error occurs before it can be credited to another account, the entire transaction must fail. The money cannot be lost or taken from one account without being successfully deposited into the other.</p>
 <h3 class="anchored_heading" id="consistency">Consistency</h3>
-<p><em>Consistency</em> refers to the state the data is in when certain conditions are met. For example, one rule may be that each invoice must relate to a customer in the customer table. These rules may be broken during the course of a transaction if, for example the invoice is inserted without a related customer, which is added at a later stage in the transaction. These temporary violations are not visible outside of the transaction, and will always be resolved by the time the transaction is complete.</p>
+<p><em>Consistency</em> ensures that data adheres to predefined rules or constraints. For example, a rule might state that each invoice in the invoices table must be linked to a customer in the customers table. During a transaction, these rules can be temporarily violated—such as inserting an invoice before adding the related customer—but only within the transaction itself. These temporary violations are not visible outside the transaction and are always resolved before the transaction is finalized.</p>
 <h3 class="anchored_heading" id="isolation">Isolation</h3>
-<p><em>Isolation</em> means that any data being used during the processing of one transaction cannot be used by another transaction until the first transaction is complete. For example, if two people deposit $100 into another account with a balance of $900, the first transaction must add $100 to $900, and the second must add $100 to $1000. If the second transaction reads the $900 before the first transaction has completed, both transactions will seem to succeed, but $100 will have gone missing. The second transaction must wait until it alone is accessing the data.</p>
+<p><em>Isolation</em> ensures that data being used by one transaction is inaccessible to other transactions until the first transaction is complete. For example, if two people deposit $100 each into an account with a balance of $900, the first transaction must update the balance to $1,000, and the second must then update it to $1,100. If the second transaction reads the $900 balance before the first transaction finishes, both transactions will appear successful, but $100 will be lost. The second transaction must wait until the first completes to access the correct balance.</p>
 <h3 class="anchored_heading" id="durability">Durability</h3>
-<p><em>Durability</em> refers to the fact that once data from a transaction has been committed, its effects will remain, even after a system failure. While a transaction is under way, the effects are not persistent. If the database crashes, backups will always restore it to a consistent state prior to the transaction commencing. Nothing a transaction does should be able to change this fact.</p>
+<p><em>Durability</em> guarantees that once a transaction is committed, its effects are permanent, even in the event of a system failure. While a transaction is in progress, its changes are not yet permanent. If the database crashes before the transaction is committed, the system can be restored to a consistent state using backups, which reflect the state before the transaction started. A committed transaction cannot be undone by a failure.</p>
 
     </div>
 

diff --git a/archive/en/dbforge-data-compare/+comments/feed/index.html b/archive/en/dbforge-data-compare/+comments/feed/index.html
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: dbForge Data Compare</title><link>https://mariadb.com/kb/en/dbforge-data-compare/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/dbforge-data-compare/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Mon, 30 Sep 2024 03:29:31 +0000</lastBuildDate></channel></rss>
+<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: dbForge Data Compare</title><link>https://mariadb.com/kb/en/dbforge-data-compare/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/dbforge-data-compare/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Fri, 04 Oct 2024 00:03:36 +0000</lastBuildDate></channel></rss>
diff --git a/archive/en/dbforge-data-compare/+comments/index.html b/archive/en/dbforge-data-compare/+comments/index.html
@@ -31,7 +31,7 @@
 Comments - dbForge Data Compare
 " />
     <meta property="og:type" content="article" />
-    <meta property="og:url" content="https://mariadb.com/kb/en/dbforge-data-compare/+comments" />
+    <meta property="og:url" content="https://mariadb.com/kb/en/dbforge-data-compare/+comments/" />
     <meta property="og:image" content="http://mariadb.comaskmonty-logo.png" />
     <meta property="og:site_name" content="MariaDB KnowledgeBase" />
     <meta property="fb:admins" content="514852603" />
@@ -76,7 +76,7 @@
                 </li>
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/dbforge-data-compare/+comments"> Login</a>
+                        <a href="/kb/user/login?next=/kb/en/dbforge-data-compare/+comments/"> Login</a>
                     </li>
 
             </ul>
@@ -121,7 +121,7 @@
 
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/dbforge-data-compare/+comments" rel="nofollow">Login</a>
+                        <a href="/kb/user/login?next=/kb/en/dbforge-data-compare/+comments/" rel="nofollow">Login</a>
                     </li>
 
 

diff --git a/archive/en/dbforge-data-compare/+source/index.html b/archive/en/dbforge-data-compare/+source/index.html
@@ -315,7 +315,7 @@ <h1>dbForge Data Compare - Source</h1>
     <div class="revision_info">
         <dl class="table">
             <dt>Revision</dt>
-            <dd><a href="/kb/en/dbforge-data-compare/+r/134958/">134958</a></dd>
+            <dd><a href="/kb/en/dbforge-data-compare/+r/143754/">143754</a></dd>
             <dt>User</dt>
             <dd>
 <span class="user" id="user-1936">
@@ -324,7 +324,7 @@ <h1>dbForge Data Compare - Source</h1>
             <dt>Date</dt>
             <dd>
 
-<span class="datetime" title="2024-02-05 09:59">2024-02-05 09:59</span></dd>
+<span class="datetime" title="2024-10-03 12:06">2024-10-03 12:06</span></dd>
         </dl>
     </div>
 
@@ -398,6 +398,7 @@ <h1>dbForge Data Compare - Source</h1>
 
 &lt;&lt;style class=&#34;centered graybox&#34;&gt;&gt;
 |= Version |= Introduced
+|  dbForge Data Compare 10.1   |  Support for the rds-ca-rsa2048-g1 SSL/TLS certificate for connecting to MariaDB servers on AWS and enhanced cloud compatibility features, new automation capabilities
 |  dbForge Data Compare 10.0   |  Support for MariaDB 11.4, Added support for temporal tables in MariaDB
 |  dbForge Data Compare 5.9     |  Support for MariaDB 11.3
 |  dbForge Data Compare 5.8     |  Support for MariaDB 10.9, Support for MariaDB 10.10

diff --git a/archive/en/dbforge-data-compare/index.html b/archive/en/dbforge-data-compare/index.html
@@ -279,7 +279,7 @@
         <dt>Modified</dt>
         <dd>
 
-<span class="datetime" title="2024-02-05 09:59">7 months, 3 weeks ago</span></dd>
+<span class="datetime" title="2024-10-03 12:06">11 hours, 57 minutes ago</span></dd>
 
         <dt>Type</dt>
         <dd>article</dd>
@@ -481,6 +481,7 @@ <h3 class="anchored_heading" id="8-export-comparison-results">8. Export Comparis
 <p>Download a free 30-day trial of dbForge Data Compare <a href="https://www.devart.com/dbforge/mysql/datacompare/download.html">here</a>.</p>
 <p><a href="https://docs.devart.com/data-compare-for-mysql">Documentation</a></p>
 <div class="cstm-style centered graybox"><table><tr><th>Version</th><th>Introduced</th></tr>
+<tr><td>dbForge Data Compare 10.1</td><td>Support for the rds-ca-rsa2048-g1 SSL/TLS certificate for connecting to MariaDB servers on AWS and enhanced cloud compatibility features, new automation capabilities</td></tr>
 <tr><td>dbForge Data Compare 10.0</td><td>Support for <a href="/kb/en/what-is-mariadb-114/">MariaDB 11.4</a>, Added support for temporal tables in MariaDB</td></tr>
 <tr><td>dbForge Data Compare 5.9</td><td>Support for <a href="/kb/en/what-is-mariadb-113/">MariaDB 11.3</a></td></tr>
 <tr><td>dbForge Data Compare 5.8</td><td>Support for <a href="/kb/en/what-is-mariadb-109/">MariaDB 10.9</a>, Support for <a href="/kb/en/what-is-mariadb-1010/">MariaDB 10.10</a></td></tr>

diff --git a/archive/en/dbforge-data-generator/+comments/feed/index.html b/archive/en/dbforge-data-generator/+comments/feed/index.html
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: dbForge Data Generator</title><link>https://mariadb.com/kb/en/dbforge-data-generator/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/dbforge-data-generator/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Mon, 30 Sep 2024 03:29:37 +0000</lastBuildDate></channel></rss>
+<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: dbForge Data Generator</title><link>https://mariadb.com/kb/en/dbforge-data-generator/+comments/feed/</link><description></description><atom:link href="https://mariadb.com/kb/en/dbforge-data-generator/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Fri, 04 Oct 2024 00:03:56 +0000</lastBuildDate></channel></rss>
diff --git a/archive/en/dbforge-data-generator/+comments/index.html b/archive/en/dbforge-data-generator/+comments/index.html
@@ -31,7 +31,7 @@
 Comments - dbForge Data Generator
 " />
     <meta property="og:type" content="article" />
-    <meta property="og:url" content="https://mariadb.com/kb/en/dbforge-data-generator/+comments" />
+    <meta property="og:url" content="https://mariadb.com/kb/en/dbforge-data-generator/+comments/" />
     <meta property="og:image" content="http://mariadb.comaskmonty-logo.png" />
     <meta property="og:site_name" content="MariaDB KnowledgeBase" />
     <meta property="fb:admins" content="514852603" />
@@ -76,7 +76,7 @@
                 </li>
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/dbforge-data-generator/+comments"> Login</a>
+                        <a href="/kb/user/login?next=/kb/en/dbforge-data-generator/+comments/"> Login</a>
                     </li>
 
             </ul>
@@ -121,7 +121,7 @@
 
 
                     <li>
-                        <a href="/kb/user/login?next=/kb/en/dbforge-data-generator/+comments" rel="nofollow">Login</a>
+                        <a href="/kb/user/login?next=/kb/en/dbforge-data-generator/+comments/" rel="nofollow">Login</a>
                     </li>