[5.0] Disable MySQL strict mode #11008
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -46,12 +46,19 @@ public function connect(array $config) | |||
| )->execute(); | |||
| } | |||
|
|
|||
| // If the "strict" option has been configured for the connection we'll enable | |||
| // strict mode on all of these tables. This enforces some extra rules when | |||
| // If the "strict" option has been configured for the connection we will setup | |||
There was a problem hiding this comment.
Spaces must be used to indent lines; tabs are not allowed
|
Please send to 5.1. 5.0 is closed for changes. |
|
This is already merged on 5.1, i only got these changes from there to 5.0... I know 5.0 is closed for changes, but as i said, everyone that still uses laravel 5.0 and gets the new homestead box will see this timestamp column error... Not sure if 5.0 is still being heavily used... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm basically moving #9712 from
5.1to5.0, now with latest homestead version which comes with MySQL 5.7, all migrations are broken because of this new restriction.