Okay my actual like system is kinda energy-intensive regarding api requests. So im going for a fresh start. Ive got a collection movie_liked who gonna store all movie likes. Each document gonna as :
- userID
- movieID My first problem, is how prevent when liking, not have duplicate like for the same user with the same movie ? There no solution without making a check before (listDocument,....) ?
Ideally, I would like to have a single request to like or dislike a movie (like on Youtube, etc...) but I guess for that we need to have a custom backend with custom api request
You can add 1 unique index on userId and movieId
Yeah my bad. But right now I try to create an api route in my NextJS app like this :
/api/user/${userId}/movie/${movieId}/like for the like, but Ive got an error about user_unauthorized. That weird because its working with function, but not with api routes. I guess its because when using api routes, we dont have the user token to authorize the request
You're right. The session is client side and there is no session server side
Recommended threads
- Next16 server side and client side
I want to use AppWrite in a Next.16 project. Following the documentation, I implemented server-side authentication using Node-AppWrite. Is it possible to make a...
- In operator
can we have in operator or if you can suggest any workaround
- Having problems with Appwrite API keyAny...
Having problems with Auth as a result of the API key Anyone to help asap?