Skip to content
TidesDB

Server Compatibility

Server Compatibility

TideSQL is built against a server source tree and tracks that server’s storage-engine interface, so a given TideSQL release targets specific server versions. The table records which have been tested and confirmed working. Full support means the engine is tested against all known functionality on that server version.

Server versionMinimum TideSQL versionFull support
Percona Server 8.0.46-372.1.0Yes
Percona Server 8.4.11-112.1.0Yes
Percona Server 9.7.2-22.1.0Yes

Percona’s lines after 9.7 are not tested. A plugin is built against one exact server release and loads only into that release; see Installing TideSQL.

This is the TideSQL 2.x manual and it pairs with TidesDB v10. The current pinned release is 2.1.0, linking TidesDB v10.2.1, at beta maturity. A 2.x minor or patch links a TidesDB v10 release and extends this same manual, so only a new major opens a new manual. See Versioning for how the plugin and the library versions relate.

As versions are tested and confirmed working this table is updated.

What differs between the lines

One source builds on every line above. Where a server release changed something the engine depends on, the difference is absorbed at build time, and most of it is invisible from SQL. What is not:

Behaviour8.08.49.7
VECTOR columnsNot available — the type arrived in 9.0Not availableStored, read back and ranked by DISTANCE; no vector index; see Vector Columns
Writing InnoDB and TidesDB in one transactionAllowedAllowedAllowed, with deprecation warning 6414

Every line shares one difference from stock MySQL. Percona Server refuses a range write or a locking read at REPEATABLE READ inside a multi-statement transaction when the engine reports it takes no gap locks. TideSQL reports that it does, so those statements run as they would on stock MySQL; Transactions and Isolation says what that means for phantoms.

A cascading foreign key behaves identically on every line, though the server’s part in it differs. From 9.6 the server opens every child table a cascade may reach before the statement starts. Before that it only takes the child’s metadata lock, and the engine opens the child itself, under that lock, for as long as the cascade runs.

What the server offers an engine

Some of what a storage engine can do is the engine’s own; the rest is whatever the server hands it. This is the second kind — the capabilities Percona Server does or does not offer, and how TideSQL reaches each one. The manual says so again at the point each matters:

CapabilityOn Percona Server
Per-table storage optionsThrough ENGINE_ATTRIBUTE; see Table Options
Per-row expiry columnThrough a column’s ENGINE_ATTRIBUTE; see Time-To-Live
Encryption key custodyA keyring component, two-tier; see Data-at-Rest Encryption
Partitioned tablesNot available; see Partitioning
System-versioned tablesNot available — the server has no system versioning
Multi-primary clusteringNot available; see Replication and High Availability
Column histogramsANALYZE TABLE ... UPDATE HISTOGRAM, sampled by the engine; see Table Maintenance
Bulk loadNot available — the server’s loader needs a driver component Percona Server does not ship; see Limitations
Foreign keysEnforced by the engine, with the shape restrictions in Limitations

A database written by one TideSQL build is readable by any other at the same version: the column families, the row format, the key encoding and the engine’s own metadata are fixed by the linked TidesDB release rather than by the server. See Versioning for the rollback boundary that follows from it.