Skip to content

Conversation

@guvra
Copy link
Collaborator

@guvra guvra commented Aug 29, 2025

This PR enables the strict_schema option by default (except in config templates, e.g. magento2).

This is a breaking change.
When this mode is enabled, the dump creation fails if the configuration file contains undefined table names.
An error is also triggered if a pattern (e.g. log_*) does not match any existing table.

The default is still false in config templates because depending on the framework version and edition, some tables may or may not exist.

@guvra guvra force-pushed the feat-strict-mode-enabled branch 2 times, most recently from d492ea9 to 48e9e66 Compare August 29, 2025 21:50
@guvra guvra force-pushed the feat-strict-mode-enabled branch 7 times, most recently from 4d36b4e to 7c7af11 Compare August 30, 2025 20:59
@guvra guvra force-pushed the feat-strict-mode-enabled branch from 7c7af11 to 611925d Compare September 3, 2025 22:46
@guvra guvra force-pushed the feat-strict-mode-enabled branch from 611925d to 31d8b8f Compare September 3, 2025 22:52
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

Successfully merging this pull request may close these issues.

2 participants