-
Notifications
You must be signed in to change notification settings - Fork 298
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
Mysql 5.7: Installation error with default data on many tables #5
Comments
Thank you for this bug report. Can you tell me which operating system and php/mysql versions you are using so that we can reproduce the issue? |
@stripthis I've sent the diff file to your email |
@imami Sorry this is taking longer than expected, but this format is actually generated by cakephp schema tools, so it's not something we're willing to change without understanding the full impact. Thanks for your patience. |
Hello. It happens with Php 5.4 as well. After the fix provided by imami all works. |
Thanks for the hint @anogues, I think this issue is due to strict mode becoming the default on Mysql 5.7, and the fixtures not enforcing some of the "cannot be null" rules, like with permission_type.description. We'll look into this now that we can reproduce the issue. |
@anogues @imami, we released a fix for Mysql5.7 schema issues just now. It will still cause issues with sql_mode only_full_group_by enabled, but it should work fine with strict mode now. Please open a new issue c if you run into issues again! See. https://www.passbolt.com/release/notes#v1.1.0 |
during the installation process, there was so many of errors like this.
when I fix one, I get another error for another table/field
I finally find the solution in one of this two ways:
A: In
app/Config/Schema/schema.php
Replace all
array('type' => 'string', 'null' => false, 'default' => null,
with
array('type' => 'string', 'null' => false, 'default' => '',
B: In this directory
app/Plugin/DataDefault/Console/Command/Task/
check files ony by one to fix default data , and add the missing value for some string fields
Obviously I choose the first way for my case. but I think this issue is better to be fixed soon
The text was updated successfully, but these errors were encountered: