Fix 'revoked' datatype consistency #1678
Closed
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.
Summary
Column
revoked
within database is created with datatype boolean.When using JWT library together with pgbouncer which is running in transaction pooling mode and db(postgres) configuration within laravel with options:
throws error:
Problem:
In the current code, there are some calls where the column 'revoked' is addressed using integers, while in other places, it is addressed using booleans.
Solution:
This fix ensures consistency within the PHP code by ensuring that all calls using the
revoked
column utilize the boolean data type, thereby maintaining a uniform coding style and preventing the switching between different data types.