MariaDB

MySQL is the default database used by much of the Linux system. It is maintained by Oracle Corporation (originally Sun Microsystems) and is licensed under the GNU GPL v2 license.

Examples of programs using this include:

Amarok music player
Akonadi PIM subsystem (KDE)
MediaWiki
Many other content management systems

Setting up MySQL for the first use

You will need to set the root password. This is like the root account on Linux, it allows full control over MySQL. Make sure this password is kept secure at all times. Many of the programs that require the MySQL database will require root access initially to make the tables they require.

Chaning the root password

Open Konsole
At the command prompt, type:
```
# mysqladmin -u root password newpassword
```
For example, if you wanted to change your password to computer, type:
```
# mysqladmin -u root password computer
```
Remember, you password is in plain sight on the command prompt. Make sure no one sees you typing and clear the screen afterwards by typing at the prompt:
```
# clear
```
You may also want to clear your scrollback. This can be done in the 'Tools' menu of Konsole.
Test your new password by logging into MySQL. Type at the prompt:
```
# mysql -u root -p
```
Type your password when asked.
If you've logged in OK, exit by typing:
```
mysql> exit;
```
(Don't forget the ;). MySQL will respond with 'Bye' if you have correctly exited and return you to the prompt.
If your stuck and MySQL is returning -> 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.

Configuring MySQL

There are a few things you may want to change with MySQL, depending on how you plan on using MySQL.

InnoDB separate tables

By default, MySQL 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 ibdata1. 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.
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 the database dropping the table and then importing the database again.

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:

Goto the Launch Menu and launch Kwrite.
You then need to goto 'File' on the menu bar and click 'Open'.
You now need to open the MySQL configuration file. This is located at /etc/my.cnf.

Scroll down and find the block (values edited out for security):

 # The MySQL server
 [mysqld]
 port            = 3306
 socket          = /<dir>/mysql.sock
 # Change following line if you want to store your database elsewhere
 # datadir = /<dir>
 skip-external-locking
 key_buffer_size = <num>M
 max_allowed_packet = <num>M
 table_open_cache = <num>
 sort_buffer_size = <num>K
 net_buffer_length = <num>K
 read_buffer_size = <num>K
 read_rnd_buffer_size = <num>K
 myisam_sort_buffer_size = <num>M

At the end of the block, you will need to add the following:
```
innodb_file_per_table=1
```
Now save this change and close the file.
For the change to take effect, you will need to restart the MySQL server.
- Goto the Lanuch menu and open Konsole
- At the prompt type rcmysql restart. This can take a few seconds.
- Now type rcmysql status. 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 typed the directive correctly and have placed it in the correct block.

Binary logging

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 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.

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.
You then need to goto 'File' on the menu bar and click 'Open'.
You now need to open the MySQL configuration file. This is located at /etc/my.cnf.

Scroll down and find the block:

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

You now need to comment out the lines log-bin=mysql-bin and binlog_format. This is done by adding a # to the beginning of the lines. Once commented out, the block should look like this: # Replication Master Server (default) # binary logging is required for replication # log-bin=mysql-bin # binary logging format - mixed recommended # binlog_format=mixed


Now save this change and close the file.
For the change to take effect, you will need to restart the MySQL server.
 Goto the Lanuch menu and open Konsole
 At the prompt type rcmysql restart. This can take a few seconds.
 Now type rcmysql status. 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 # in front of the lines of code shown.

Related Articles

Importing a MySQL database
Exporting a MySQL database

External

MySQL website