The K Desktop Environment

Next Previous Table of Contents

3. Basic Usage

3.1 The main screen

Here you can select your activates you want to do. First you have to login into a server.If you are disconnected all other buttons and Menu-entries are disabled. If your are connected, you can see some infos about the server you are connected to and about the build-in client-lib of mysql.

Login

(re-)connect to a sql-server

Grants

Edit the grants of users/hosts on current connected SQL-server

Status

shows a box with status-information about the sql-server. This information are updated ones a minute. In following version, the polling intervall will be changeable.

Thread

shows the current threads on the sql-server.

Create DB

Create a new database>

Create Table and Alter Table

Create or alter tables. Since release 0.3 these should work fine, it were realy hard to implement.

3.2 Login to a server

Click on the "login" - button of the main window. A little dialog comes up, where you can enter the needed information:

Host

The host name to connect to. If you leave this blank, it trys to connect to the localhost via UNIX-socket. If this does not work try out 127.0.0.1 so kmysqladmin trys to connect via tcp/ip to the localhost

User

The user name you want connect as. If you don't enter a name, it uses the login name.

Password

The password for the user@host. It's a hidden input, and kmysqladmin don't save it on any place.

Port

If connect via tcp/ip, use this port. Most mysql-server listen on 3306.

3.3 Logoff

Simple click on

"File" -> "Disconnect"
and kmysqladmin will close the connection to the current sql-server.

3.4 Logging your work

kmysqladmin logs all your steps into the main log window. So you can look, whats going up. Error-message will also appear there. In most cases, if a statement fails, an errbox comes up and you should take a look to the log-window to resolve whats going on. Well, these error messages are the messages of the server, not my. Will say, if you cannot interpret that, please take a look to the mysql - documentation. I'll bring my error-messages only to errorboxes.

Writing logfiles

If you want to log into a file to, select

"File" -> "Write log to file"
and select a filename. kmysqladmin will overwrite any existing file, so be carefull. It is a way to get sql-scripts for instance if you build new databases on more than on server. Take after your work the file, filter out all not-needed messages and use
mysql < file
for your script. In one of the next versions I build a script generator and reader.

Empty logwindow

Simply click

"File" -> "empty window"
and all output is removed from the logwindow. If your logging into a file, the file contents aren't destroyed of course.

3.5 Status

Overall status of sql-server

This dialog shows up a status of the current used sql-server. It will refresh this information every 60 seconds. In next releases I'll let the user set a own refresh intervall. Until you don't close the connection to the server, the information in this dialog will not lost, only hidden, if you click on the "Close" - button. If you hide the dialog, it contents will not refreshed until re-open it.

Threads of the sql-server

Shows current threads using the sql-server. It works much like the status view, means, refresh every 60 seconds, no destroy of contents until connection closed etc.

Next Previous Table of Contents