Skip to content
This repository was archived by the owner on Jun 2, 2025. It is now read-only.

Table engine support #24

Closed
JanJakes opened this issue Mar 5, 2025 · 1 comment
Closed

Table engine support #24

JanJakes opened this issue Mar 5, 2025 · 1 comment

Comments

@JanJakes
Copy link
Contributor

JanJakes commented Mar 5, 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: #21 (comment)

@JanJakes JanJakes mentioned this issue Mar 5, 2025
@JanJakes
Copy link
Contributor Author

JanJakes commented Jun 2, 2025

@JanJakes JanJakes closed this as completed Jun 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant