What happened?
SQL dump uses PostgreSQL-specific syntax when exporting results in MySQL database.
The SQL dump contains PostgreSQL-specific syntax, such as double-quoted identifiers and CASCADE in DROP TABLE statements, which causes syntax errors when importing the dump into a MySQL database.
For example:
-- TablePro SQL Export
-- Generated: 2026-09-03T14:46:53Z
-- Database Type: MySQL
DROP TABLE IF EXISTS "fields" CASCADE;
INSERT INTO "fields" ("id", "process_id", "form_id", ...) VALUES (...);
Steps to reproduce
- Open a MySQL connection
- Show data from a table
- Right click and select "Export results..."
- Export using SQL option
- Try to import the SQL dump
Expected behavior
The SQL export generated from a MySQL database should contain valid MySQL syntax and should be executable against a MySQL database without syntax errors.
Database type
MySQL / MariaDB
TablePro version
0.71.0
macOS version & chip
macOS 26.6.2 Apple Silicon
Screenshots / Logs

What happened?
SQL dump uses PostgreSQL-specific syntax when exporting results in MySQL database.
The SQL dump contains PostgreSQL-specific syntax, such as double-quoted identifiers and CASCADE in DROP TABLE statements, which causes syntax errors when importing the dump into a MySQL database.
For example:
Steps to reproduce
Expected behavior
The SQL export generated from a MySQL database should contain valid MySQL syntax and should be executable against a MySQL database without syntax errors.
Database type
MySQL / MariaDB
TablePro version
0.71.0
macOS version & chip
macOS 26.6.2 Apple Silicon
Screenshots / Logs