MySQL / MariaDB
Connect to a MySQL database and set up a workspace.
Last updated
Was this helpful?
Connect to a MySQL database and set up a workspace.
Last updated
Was this helpful?
Before you begin, gather this connection information:
Name of the server that hosts the database you want to connect to and port number
User name and password
Are you connecting to an SSL server?
Launch Syntho and select Connect to a database, or under Create workspace, select MySQL / MariaDB. For a complete list of data connections, select More under To a Server. Then do the following:
Enter the name of the server that hosts the database.
Enter the database name to connect to the contained database.
Enter the port number.
Leave the protocol as-is. Only in very specific circumstances you may want to change this.
Enter the user name and password.
Select the Require SSL option when connecting to an SSL server.
Select Create workspace. If Syntho can't make the connection, verify that your credentials are correct. If you still can't connect, your computer is having trouble locating the server. Contact your network administrator or database administrator.
Columns with the data type SET are not supported.
Our MySQL and MariaDB connector, utilizing SQLAlchemy, presents certain limitations that may impact your operations:
Backtick Characters in Names: While MySQL supports the use of backtick characters (`) in table and column names by escaping them, SQLAlchemy fails to escape these characters correctly. This can result in mismatches during table and column referencing in read or write operations.
Empty SET Data Type: MySQL allows defining columns with an empty SET
definition (SET('')
). However, SQLAlchemy does not support this edge case, which may lead to issues when working with SET
data types.
The table below outlines the support for various data types in terms of generator type, and if any additional processing is performed by Syntho to successfully generate and write the data.
INTEGER
discrete
TINYINT
discrete
SMALLINT
discrete
MEDIUMINT
discrete
BIGINT
discrete
FLOAT
continuous
DOUBLE
continuous
DOUBLE PRECISION
continuous
DECIMAL
continuous
CHAR
categorical
VARCHAR
categorical
TEXT
categorical
LONGTEXT
categorical
TINYTEXT
categorical
MEDIUMTEXT
categorical
BINARY
bytes
False
False
False
False
VARBINARY
bytes
False
False
False
False
BLOB
bytes
False
False
False
False
TINYBLOB
bytes
False
False
False
False
MEDIUMBLOB
bytes
False
False
False
False
LONGBLOB
bytes
False
False
False
False
DATE
datetime
False
TIME
datetime
False
DATETIME
datetime
False
TIMESTAMP
datetime
False
YEAR
datetime
False
BIT
discrete
JSON
json
False
False
False
ENUM
sets
False
False
False
False
SET
sets
False
False
False
False
BOOL
discrete
BOOLEAN
discrete
POINT
no active support
False
True
True
True
GEOMETRY
no active support
False
True
True
True
LINESTRING
no active support
False
True
True
True
POLYGON
no active support
False
True
True
True
MULTIPOINT
no active support
False
True
True
True
MULTILINESTRING
no active support
False
True
True
True
MULTIPOLYGON
no active support
False
True
True
True
GEOMETRYCOLLECTION
no active support
False
True
True
True
Data types that are labeled as "no active support" mean that they are not actively supported, however, you may still be able to apply generators (e.g., AI-powered generation, mask, mockers or calculated columns) to these columns. Duplication is fully supported for these types.