Data Engines

DLATK offers two types of data engines: MySQL and SQLite.


MySQL is the default data engine. Settings are passed to the data engine through a configuration file. By default DLATK tries to read from ~/.my.cnf. You can pass a configuration file to DLATK with --mysql_config_file. For example, if your config file was located at /home/your_username/mysql/config.txt then you would add the following to your command: --mysql_config_file /home/your_username/mysql/config.txt

We recommand that all configuration files have at least user, password, and host defined. Here is an example of this basic configuration:


Python MySQL dependecies are not automatically installed with DLATK. To install them you can use pip or conda. For example,

pip install mysqlclient
pip install SQLAlchemy

The following versions are known to work with DLATK v1.2.0 in Python 3.8:

pip install 'mysqlclient==2.0.1'
pip install 'SQLAlchemy==1.3.20'


The data packaged with DLATK is formatted for MySQL. To use SQLite you must first convert these MySQL dumps to a SQLite database. You can do this with the mysql2sqlite package. Clone this package with

git clone

Next, we convert the MySQL dumps to SQLite databases:

cd mysql2sqlite
./mysql2sqlite /path/to/dlatk/data/dla_tutorial.sql | sqlite3 /path/to/dlatk/data/dla_tutorial.db
./mysql2sqlite /path/to/dlatk/data/dlatk_lexica.sql | sqlite3 /path/to/dlatk/data/dlatk_lexica.db

In order switch from the default MySQL to SQLite you need to add the following flag to your commands --db_engine and use the full path of the SQLite db file. For example,

dlatkInterface.p  --db_engine sqlite -d /path/to/dlatk/data/dla_tutorial

The Python dependency for SQLite (sqlite3) is part of the standard library, so no additional packages are necessary.