Hey there o/
Just a quick sidenote - Recently joined the student program and i'm loving what appwrite is providing me with. It's an amazing backend, but i'm also having a few pain points i would like to talk about.
I'm curious as to how one is supposed to do a not in query. For example, imagine i have two collections with a one sided relation between them.
Collection A has some product data, Collection B has a description and score for a product in the A collection and that B record belongs to a user. (basically, a user can only grade a product from the A collection once)
My goal was to visualise this on the frontend and offer a nice ui for it, however due to my lack of knowledge (since i'm still a student) and no previous experience with such document databases (even though we are on top of mariadb), i found it incredibly difficult to do so.
I had to basically walk over the entire B table, retrieving records that belonged to the user, then proceded to retrive records from table A and discarding them on the frontend if any of them were already being pointed at by a record in B (since that would mean that the A records was already graded by a B record and there is nothing to do)
So here i am posting about this
Since i tried to search only for this. I was pretty sure that if there existed a query like Query.notequal('$id', [....all the ids i do not want to see.....]) my life wouldve been a lot easier
But perhaps i'm way too used to relational databases and my approach is wrong
Could someone people give me a few pointers on what can be improved here because i feel so lost
Recommended threads
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- Retrieving Data From Backups
Hiya, I have a user requesting for data they accidentally deleted. I don't have document history built into my app. Is there a way to extract data from the auto...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...