Text user interface MySQL client
MitzaSQL is a free Python3 TUI MySQL client for Linux which aims to provide an easy-to-use console alternative to GUI clients. It is not meant to be a full-fledged GUI client, it only provides a read-only view of the database, though you can manipulate the data by using raw SQL queries. Some of the main features are:
- Manage multiple sessions
- View databases
- View list of tables, sql views & stored procedures in a database
- View rows in a table or sql view:
- Easily sort table data
- Filter table data using VIM-like commands (
- SQL Query editor with syntax highlighting
- VIM style keyboard shortcuts
- VIM style commands with autocomplete support
- Macros support
- Python3 (3.5 - 3.8)
- MySQL (5.5 - 8)
By default MitzaSQL stores connection credentials in plain text files in your home directory. If security is a concern you could store the file in an encrypted partition/directory and specify the path to the session file when the program starts using the
--sessions_file /path/to/sessions.ini flag. Another option would be not to persist the connection credentials when creating a new session.
Performance & known issues
Loading large datasets will slow down the rendering. By default, when opening a table screen only the first 100 records are loaded. The rest of the data is loaded automatically when scrolling down. When running queries with the SQL Query editor make sure you don't load a large number of records or else your user experience might suffer.
pip3 install mitzasql
Docker is only required for running the integration tests, testing during feature development can be done with tox alone (see below).
Run the development version
# If your currently installed Python version != 3.6 use TOXENV to specify it
tox -e dev
To run the program using a different Python version using Docker:
./run-in-docker.sh [python version] [mysql version]
# ./run-in-docker.sh 36 mysql55
tox -e dev
The testing process uses tox & Docker to automate running the tests against multiple versions of Python and MySQL servers.
During feature development Docker is not really necessary, I use it to run the test MySQL server but it that can be installed directly on the host. If that is the case, then new connection details have to be specified using environmental variables (see
tests/db/connection_fixture.py for more details).
To run the tests during feature development run:
cp env.template .env # necessary if using Docker
docker-compose up # necessary if using Docker
To generate code coverage:
Code coverage is generated in the
test-mitzasql.sh for more info.
test-mitzasql-ui.sh for more info.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.