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
The database column "priority" is defined as NOT NULL if you use the DbalContext class to generate the schema.
The default priority of a DbalMessage is 0.
The fetchPrioritizedMessage() method from the DbalConsumer class fetches messages where the priority IS NOT NULL, so all of them.
Consequently, fetchMessage(), which fetches the oldest message first, is never called as long as there are any messages left in the queue.
The priority column should be nullable and the default priority should also be null in my opinion.
The text was updated successfully, but these errors were encountered:
@f7h would you like to send us a PR?
Sorry, something went wrong.
No branches or pull requests
The database column "priority" is defined as NOT NULL if you use the DbalContext class to generate the schema.
The default priority of a DbalMessage is 0.
The fetchPrioritizedMessage() method from the DbalConsumer class fetches messages where the priority IS NOT NULL, so all of them.
Consequently, fetchMessage(), which fetches the oldest message first, is never called as long as there are any messages left in the queue.
The priority column should be nullable and the default priority should also be null in my opinion.
The text was updated successfully, but these errors were encountered: