Please sign in to comment.
Strict mode usage user-friendliness improvements
Since v1.0.5, Skeema has defaulted to using strict-mode settings for its sessions: innodb_strict_mode and a strict sql_mode. This is generally a good practice, but can cause confusing errors in Skeema when operating on databases that are not strict-mode compliant. The most common conflicts are ROW_FORMAT clauses (see #40) as well as zero-date defaults for date/datetime/timestamp columns. This commit makes two improvements regarding user-friendliness: * `skeema init` now detects if at least one table isn't strict-mode compliant, and automatically puts `connect-options` into the .skeema file to disable strict-mode when interacting with this instance. * `skeema diff` and `skeema push` now provide explanatory text when the a .sql file cannot be executed for reasons that may relate to strict-mode.
- Loading branch information...
Showing with 46 additions and 4 deletions.