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
From my understanding to source code of lucia uesr handling is used for checking if user exists in db if yes will return the properties we want else we will delete the session made that request , this aprouch have alot of cons :
make unnessesary query at most of the protected routes witch translated to un wanted delay
preventing us from making adapters for redis or any db that should only handle sessions without making our hands dirty with illegal workarounds and adapters 😂
make the idea of making guest session also need to have it's illegal adapter
what we are trying to achive is already beign achived by sql databases by making a onDelete:cascade for our relation
making building adapters harder as we will write more code
making more config and if I wanted to retrive spisific user data in a end point and other data on ther i have to make separate query or take all data in the config and retrive unnessesary data
I think we talked about this topic before on discord but as this topic apeared again and I didn't find a clear state saying what we are going to do about it so I wanted know .
The text was updated successfully, but these errors were encountered:
Package
lucia
Description
From my understanding to source code of lucia uesr handling is used for checking if user exists in db if yes will return the properties we want else we will delete the session made that request , this aprouch have alot of cons :
illegal
adapteronDelete:cascade
for our relationI think we talked about this topic before on discord but as this topic apeared again and I didn't find a clear state saying what we are going to do about it so I wanted know .
The text was updated successfully, but these errors were encountered: