Prepared statements failing (mysql/MariaDB, sqlpad > 4.3)

Running sqlpad 4.4 and latest (from docker hub; MariaDB container pinned to 10.5.3) i can’t use prepare/execute statements. Even simple examples based on https://mariadb.com/kb/en/prepare-statement/#example fail:

PREPARE stmt FROM 'SELECT @x;';
SET @x = 1;
EXECUTE stmt;

–> ER_UNKNOWN_STMT_HANDLER: Unknown prepared statement handler (stmt) given to EXECUTE

SET @table = "some_table";
SET @sql = CONCAT('SELECT * FROM ', @table);
PREPARE stmt FROM @sql;
EXECUTE stmt;

–> ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'NULL' at line 1

Both examples work with sqlpad 4.3 (from docker hub) and using MariaDBs console.

[rickbergfalk]

Yeah it is all related.

Once the updated implementation lands it’ll allow for transactions across query executions. The underlying database connection will be held open and kept alive while browser tab is open. If user opts into it that is. Otherwise if falls back to 1 query run = one connection. (or today in the event your query has many statements, it could be many connections)

[rickbergfalk]

Fix for this will be in latest docker image. Limits are enforced by sql-limiter now so there could potentially be some quirks introduced with that… hopefully not though.