You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the database session driver, I'm frequently getting QueryExceptions thrown because a duplicate session id is trying to be inserted. A simple check to see if the session id exists in the database, before inserting would fix this. Alternatively, a better way of the id being generated would remove the need for an extra query.
I've seen this issue in my logs a few hundred times over the past week so it seems to be significant.
Steps To Reproduce:
N/a
The text was updated successfully, but these errors were encountered:
There's no real change in the code for DatabaseSessionHandler between 5.2 and 5.3. See the diff (only small docblock changes, and rather than using time(), the new code uses Carbon to get a timestamp.
In that case, this bug applies equally to 5.3 and should be reopened.
Description:
When using the database session driver, I'm frequently getting QueryExceptions thrown because a duplicate session id is trying to be inserted. A simple check to see if the session id exists in the database, before inserting would fix this. Alternatively, a better way of the id being generated would remove the need for an extra query.
I've seen this issue in my logs a few hundred times over the past week so it seems to be significant.
Steps To Reproduce:
N/a
The text was updated successfully, but these errors were encountered: