Skip to content

Table engine support #191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JanJakes opened this issue Jun 2, 2025 · 0 comments
Open

Table engine support #191

JanJakes opened this issue Jun 2, 2025 · 0 comments

Comments

@JanJakes
Copy link
Collaborator

JanJakes commented Jun 2, 2025

Currently, the SQLite driver saves the specified table engine in the information schema, but it doesn't emulate different engine behavior in any way, nor it checks whether the engine is supported. At the moment, we expect the engine to be InnoDB.

WordPress also works with MyISAM, and there are other table engines in MySQL.

We probably could implement support for some additional engines (ignore FKs for MyISAM, etc.), but until then, we can trigger a warning when an engine other than InnoDB is used.

Additionally, we should make the warnings configurable:

These warnings will quickly get annoying so we could add a driver-level warning control with an option such as "warnings" => array( "db_engine" => true|false, ... )

See also: Automattic/sqlite-database-integration#21 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant