Skip to content
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

[5.4] Execute queries with lock only in write database #17386

Merged
merged 2 commits into from
Jan 18, 2017
Merged

[5.4] Execute queries with lock only in write database #17386

merged 2 commits into from
Jan 18, 2017

Conversation

SebastianBerc
Copy link
Contributor

As in PR #17317 but with the better solution and I added the test as a bug proof.

/cc @JoostK, @GrahamCampbell

@SebastianBerc SebastianBerc changed the title [5.4] Execute queries with lock only in write database #2 [5.4] Execute queries with lock only in write database Jan 18, 2017
@SebastianBerc
Copy link
Contributor Author

I have no idea why StyleCI can't analysis this PR :/

@@ -49,7 +49,7 @@ public function messages()
/**
* Clear all of the messages from the local collection.
*
* @return void
* @return Collection
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't make unrelated changes in the PR. This change also doesn't match our code standards anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed commit with that.

@taylorotwell taylorotwell merged commit ed1550f into laravel:5.4 Jan 18, 2017
@SebastianBerc SebastianBerc deleted the patch-1 branch January 19, 2017 17:12
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.

3 participants