We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Undefined array key "precision"
This is a (multiple allowed):
bug
enhancement
feature-discussion (RFC)
CakePHP Version: 4.4.18
Migrations plugin version: 3.9.0
Bake plugin version (if relevant): 2.9.3
Database server (MySQL): 10.6.12-MariaDB-0ubuntu0.22.04.1
PHP Version: 8.1.22
Platform / OS: Ubuntu 22.04.3 LTS
Tried to create a migration file with
bin/cake bake migration_diff ModStCommentsUpdateDeletedBool
I made only one change to the database table. I changed the datatype from tinyint(4) to tinyint(1). Before: After:
create migration file without warning
displays a warning about Undefined array key "precision" Despite the warning, the migration was apparently created correctly.
The text was updated successfully, but these errors were encountered:
Is this still valid? Looks a bit weird when there is only int involved.
Sorry, something went wrong.
yes it still happens (I'm on cakephp 4.5.1, with migrations 3.9.0)
No branches or pull requests
This is a (multiple allowed):
bug
enhancement
feature-discussion (RFC)
CakePHP Version: 4.4.18
Migrations plugin version: 3.9.0
Bake plugin version (if relevant): 2.9.3
Database server (MySQL): 10.6.12-MariaDB-0ubuntu0.22.04.1
PHP Version: 8.1.22
Platform / OS: Ubuntu 22.04.3 LTS
What you did
Tried to create a migration file with
I made only one change to the database table.
I changed the datatype from tinyint(4) to tinyint(1).
Before:
After:
Expected Behavior
create migration file without warning
Actual Behavior
displays a warning about
Undefined array key "precision"
Despite the warning, the migration was apparently created correctly.
The text was updated successfully, but these errors were encountered: