MariaDB - Revision history

Sam: /* Binary logging */ Typo correction

2023-07-30T14:50:07Z

Binary logging: Typo correction

← Older revision		Revision as of 14:50, 30 July 2023
Line 81:		Line 81:

	<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">		<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>		</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 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.		* 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.

Sam: Grammatical changes

2022-07-13T02:07:24Z

Grammatical changes

← Older revision		Revision as of 02:07, 13 July 2022
Line 89:		Line 89:
	If you are not using a MySQL duplication server, the logging is of no use. It can be turned off by the following:		If you are not using a MySQL duplication server, the logging is of no use. It can be turned off by the following:

	* ~~Goto~~ the Launch Menu and launch Kwrite.		* Go to the Launch Menu and launch Kwrite.
	* You then need to ~~goto~~ 'File' on the menu bar and click 'Open'.		* You then need to go to 'File' on the menu bar and click 'Open'.
	* You now need to open the MariaDB configuration file. This is located at <code>/etc/my.cnf</code>.		* You now need to open the MariaDB configuration file. This is located at <code>/etc/my.cnf</code>.
	* Scroll down and find the block:		* Scroll down and find the block:
Line 109:		Line 109:
	* Now save this change and close the file.		* Now save this change and close the file.
	* For the change to take effect, you will need to restart the MariaDB server.		* For the change to take effect, you will need to restart the MariaDB server.
	* ~~Goto~~ the Lanuch menu and open Konsole		* Go to the Lanuch menu and open Konsole
	* At the prompt type <code>service mysql restart</code>. This can take a few seconds.		* At the prompt type <code>service mysql restart</code>. This can take a few seconds.
	* Now type <code>service mysql status</code>. You should see that the sever is now running. If it isn't and it says 'failed', there is a problem with what you have typed. You will need to go back through from the beginning, ensuring you have put the <code>#</code> in front of the lines of code shown.		* Now type <code>service mysql status</code>. You should see that the sever is now running. If it isn't and it says 'failed', there is a problem with what you have typed. You will need to go back through from the beginning, ensuring you have put the <code>#</code> in front of the lines of code shown.

Sam: /* Binary logging */ Grammatical changes

2022-07-13T02:05:53Z

Binary logging: Grammatical changes

← Older revision		Revision as of 02:05, 13 July 2022
Line 81:		Line 81:

	<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">		<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 ~~no effect~~ 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 will already be disabled and so don't need to be changed.'''
	</div>		</div>

Sam: /* Setting up MariaDB for the first use */ Added openSUSE 15.4 line

2022-07-13T02:04:44Z

Setting up MariaDB for the first use: Added openSUSE 15.4 line

← Older revision		Revision as of 02:04, 13 July 2022
Line 14:		Line 14:
	You will need to set the root password. This is like the root account on Linux, it allows full control over MariaDB. Make sure this password is kept secure at all times. Many of the programs that require the MariaDB database will require root access initially to make the tables they require.		You will need to set the root password. This is like the root account on Linux, it allows full control over MariaDB. Make sure this password is kept secure at all times. Many of the programs that require the MariaDB database will require root access initially to make the tables they require.

	=== ~~Chaning~~ the root password ===		=== Changing the root password ===

			'''Authentication is done by the Linux root user as of openSUSE 15.4 - log in as root and type <code>mysql</code> to login as root'''

	* Open Konsole		* Open Konsole

Sam: Added padding to warning boxes

2020-09-08T18:02:41Z

Added padding to warning boxes

← Older revision		Revision as of 18:02, 8 September 2020
Line 38:		Line 38:
	=== InnoDB separate tables ===		=== InnoDB separate tables ===

	<div style="background:#FFEEEE;border:1px solid #FF0000;">		<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
	'''MariaDB does not use the InnoDB storage engine by default. If you are using MariaDB with standard settings, these settings will have no effect and so don't need to be changed.'''		'''MariaDB does not use the InnoDB storage engine by default. If you are using MariaDB with standard settings, these settings will have no effect and so don't need to be changed.'''
	</div>		</div>
Line 78:		Line 78:
	=== Binary logging ===		=== Binary logging ===

	<div style="background:#FFEEEE;border:1px solid #FF0000;">		<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 no effect 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 no effect and so don't need to be changed.'''
	</div>		</div>

Sam: Removed unnecessary html codes, changed old MySQL section from MariaDB to MySQL and added warnings

2016-04-11T22:35:32Z

Removed unnecessary html codes, changed old MySQL section from MariaDB to MySQL and added warnings

Show changes

Sam: Small format changes

2015-02-09T00:56:28Z

Small format changes

← Older revision		Revision as of 00:56, 9 February 2015
Line 22:		Line 22:
	# Type your password when asked.		# Type your password when asked.
	# If you've logged in OK, exit by typing: <pre>mysql> exit;</pre>(Don't forget the ;). MariaDB will respond with 'Bye' if you have correctly exited and return you to the prompt.		# If you've logged in OK, exit by typing: <pre>mysql> exit;</pre>(Don't forget the ;). MariaDB will respond with 'Bye' if you have correctly exited and return you to the prompt.
	# If your stuck and MariaDB is returning <code>-></code> at any time, you have forgotten the ; at the end of the command. Type the command with a ;. This will display an error message. Type the command again with the ; and the command will work.		# If your stuck and MariaDB is returning <code>-></code> at any time, you have forgotten the ; at the end of the command. Type the command with a <code>;</code>. This will display an error message. Type the command again with the <code>;</code> and the command will work.

	== Configuring MariaDB ==		== Configuring MariaDB ==

Sam: Added MariaDB 10 upgrade section

2014-05-28T11:59:20Z

Added MariaDB 10 upgrade section

← Older revision		Revision as of 11:59, 28 May 2014
Line 31:		Line 31:

	<div style="background:#FFEEEE;border:1px solid #FF0000;">		<div style="background:#FFEEEE;border:1px solid #FF0000;">
	'''MariaDB does not use the InnoDB storage engine by default. If you are using MariaDB with standard settings, these settings will have no effect and so don't need to be ~~done~~.'''		'''MariaDB does not use the InnoDB storage engine by default. If you are using MariaDB with standard settings, these settings will have no effect and so don't need to be changed.'''
	</div>		</div>

Line 114:		Line 114:
	<pre>mysql> FLUSH PRIVILEGES;</pre>		<pre>mysql> FLUSH PRIVILEGES;</pre>
	* You can now exit the MariaDB server.		* You can now exit the MariaDB server.

			== Upgrading to MariaDB 10 ==

			In openSUSE 13.1, it is possible to update to MariaDB 10 via. the repositories system. If you do decide to upgrade, MariaDB will not run straight away after installation. To make it run, follow these steps:

			# Make sure all databases are backed up (on this server, make sure your nightly backups have exported successfully)
			# Run <code>touch /var/lib/mysql/.force_upgrade</code> - this allows the upgrade to take place
			# Run <code>service mysql start</code> - this may take a while the first time it is started as the database is being upgraded

	== Related Articles ==		== Related Articles ==

Sam: A few more MySQL's missed, website changed

2013-12-20T21:12:27Z

A few more MySQL's missed, website changed

← Older revision		Revision as of 21:12, 20 December 2013
Line 72:		Line 72:
	=== Binary logging ===		=== Binary logging ===

	MariaDB 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:		MariaDB 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 MariaDB 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 MariaDB setup. The problems with this implementation are:
	* MariaDB has to write the transaction twice, once to the table and once to the log. This slows things down.		* MariaDB has to write the transaction twice, once to the table and once to the log. This slows things down.
	* MariaDB has data stored in 2 places, doubling the disk space for each write. This is also a security issue if working with sensitive data.		* MariaDB 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 122:		Line 122:
	== External Links ==		== External Links ==

	* [~~http~~://~~www~~.~~mysql.com MySQL~~ website]		* [https://mariadb.org/ MariaDB website]

Sam: Changed InnoDB section to reflect MariaDB

2013-11-22T22:21:25Z

Changed InnoDB section to reflect MariaDB

← Older revision		Revision as of 22:21, 22 November 2013
Line 30:		Line 30:
	=== InnoDB separate tables ===		=== InnoDB separate tables ===

	By default, ~~MariaDB~~ uses InnoDB to store the information in the database. The old method, MyIASM stored the data within the database folder on the hard drive separately. InnoDB now stores this data for all created databases under one file called <code>ibdata1</code>. There are a few problems with this implementation:		<div style="background:#FFEEEE;border:1px solid #FF0000;">
			'''MariaDB does not use the InnoDB storage engine by default. If you are using MariaDB with standard settings, these settings will have no effect and so don't need to be done.'''
			</div>

			By default, MySQL uses InnoDB to store the information in the database. MariaDB uses XtraDB. The old method, MyIASM stored the data within the database folder on the hard drive separately. InnoDB now stores this data for all created databases under one file called <code>ibdata1</code>. There are a few problems with this implementation:
	* All data stored under one file means if this one file becomes corrupt, you are more likely to loose '''ALL''' the databases you have.		* All data stored under one file means if this one file becomes corrupt, you are more likely to loose '''ALL''' the databases you have.
	* A problem in InnoDB makes it so that when you drop a table, the space is not freed from the file, the table is basically unlinked from the data. This can be a security issue if you are working with sensitive data. Another problem means that the file will never shrink, the file will grow until all space is exhausted.		* A problem in InnoDB makes it so that when you drop a table, the space is not freed from the file, the table is basically unlinked from the data. This can be a security issue if you are working with sensitive data. Another problem means that the file will never shrink, the file will grow until all space is exhausted.
	* Once set up in the mode, any database created before this change will still be stored in the one file. The only way to make it use it's own table is by [[Exporting a MySQL database\|exporting]] the database dropping the table and then [[Importing a MySQL database\|importing]] the database again.		* Once set up in the mode, any database created before this change will still be stored in the one file. The only way to make it use it's own table is by [[Exporting a MySQL database\|exporting]] the database dropping the table and then [[Importing a MySQL database\|importing]] the database again.

	~~MariaDB~~ does let you fall back to the old MyIASM method of storing the data while using the InnoDB storage method still. If you want to turn this option on, you will need to do the following:		MySQL does let you fall back to the old MyIASM method of storing the data while using the InnoDB storage method still. If you want to turn this option on, you will need to do the following:

	<ol>		<ol>