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

[8.x] Add missing dispatchAfterCommit to DatabaseQueue #35715

Merged
merged 2 commits into from Dec 25, 2020
Merged

[8.x] Add missing dispatchAfterCommit to DatabaseQueue #35715

merged 2 commits into from Dec 25, 2020

Conversation

danesteve
Copy link
Contributor

The recent #35422 missed adding the new $dispatchAfterCommit parameter to the DatabaseQueue.
The new param is being passed in the DatabaseConnector but the queue class was not updated.

I also reformatted the DatabaseQueue constructor params (one arg per line) to match the changes in the previous PR.

@taylorotwell
Copy link
Member

ping @themsaid

@taylorotwell taylorotwell merged commit 08303c7 into laravel:8.x Dec 25, 2020
@themsaid
Copy link
Member

themsaid commented Dec 25, 2020

For the database queue, the dispatching will happen after commit anyway. So this PR is not needed.

@danesteve
Copy link
Contributor Author

danesteve commented Dec 25, 2020

I think it could be an issue if the transaction is happening on a different connection than the one holding your jobs table, but that can probably be considered an edge case.

In any case, feel free to revert if you think this is not needed.

EDIT: Just to make it clear, the original intent of this PR was to align the params being passed in the DatabaseConnector with the DatabaseQueue signature since there was a mismatch.

levacic pushed a commit to levacic/laravel-framework that referenced this pull request Dec 26, 2020
* add missing dispatchAfterCommit to DatabaseQueue

* add new param to phpdoc
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.

None yet

3 participants