Queue failed to unserialize if users table uses UUID as primary key #38769
Unanswered
wildangunawan
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I've been struggling to find the solution for this for a while. My current scenario is I would like to use UUID as my users table primary key. But right now, when working on queue (my scenario below is for SendEmailVerificationNotification that get pushed to queue) that is related to users, Laravel returns an error:
AFAIK, this error happened when Laravel tried to unserialize the command value. I didn't see this error when I use integer as my primary key so I suspect the UUID actually made the problem. Is there any actually issue with using UUID as primary key at users table and queue?
Ps. I think this is related to #15235 and #22?
Edit: Changing the users table to use auto increment integer does make queue to work. But I'm still interested with UUID. Is there any workaround on this?
Beta Was this translation helpful? Give feedback.
All reactions