MariaDB: Difference between revisions

Line 81:

'''MariaDB does not use binary logging or replication by default. If you are using MariaDB with standard settings, these settings will have ~~will~~ already be disabled and so don't need to be changed.'''

'''MariaDB does not use binary logging or replication by default. If you are using MariaDB with standard settings, these settings will have already been disabled and so don't need to be changed.'''

</div>

MySQL by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 MySQL server in a master-slave configuration, you can link them together and the slave reads the logs to get the same data. You more than likely won't need this if you are running a ~~standalone~~ MySQL setup. The problems with this implementation are:

MySQL by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 MySQL server in a master-slave configuration, you can link them together and the slave reads the logs to get the same data. You more than likely won't need this if you are running a stand-alone MySQL setup. The problems with this implementation are:

* MySQL has to write the transaction twice, once to the table and once to the log. This slows things down.

* MySQL has data stored in 2 places, doubling the disk space for each write. This is also a security issue if working with sensitive data.

@@ Line 81: / Line 81: @@
 <div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
-'''MariaDB does not use binary logging or replication by default. If you are using MariaDB with standard settings, these settings will have will already be disabled and so don't need to be changed.'''
+'''MariaDB does not use binary logging or replication by default. If you are using MariaDB with standard settings, these settings will have already been disabled and so don't need to be changed.'''
 </div>
-MySQL by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 MySQL server in a master-slave configuration, you can link them together and the slave reads the logs to get the same data. You more than likely won't need this if you are running a standalone MySQL setup. The problems with this implementation are:
+MySQL by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 MySQL server in a master-slave configuration, you can link them together and the slave reads the logs to get the same data. You more than likely won't need this if you are running a stand-alone MySQL setup. The problems with this implementation are:
 * MySQL has to write the transaction twice, once to the table and once to the log. This slows things down.
 * MySQL has data stored in 2 places, doubling the disk space for each write. This is also a security issue if working with sensitive data.