And docker logs appwrite
How to handle duplicates in Collection
Votes
0
Replies
24
Participants
Unknown
Messages
25
See what error shows there
Rank 2: Process
but if i dont choose unique then its working fine why?
Rank 2: Process
should i run this in terminal ? docker logs appwrite-worker-databases
Yes
Rank 2: Process
Thanks @Binyamin its working fine, but there is one problem
Rank 2: Process
AppwriteException: document_already_exists, Document with the requested ID already exists. (409)
That's good
Then you should tell the user the that attributes is already exists
Rank 2: Process
if i loged in with different account and want to create same record for that user in that is also giving me error that what i was talking previously.
Rank 2: Process
hope this time you got my point, apologies if i have not explain it properly
Got it
You want it to be unique per user?
Rank 2: Process
yes
Good.
Then delete the newly added index.
Then, create a new one and add both attributes to the index
- user ID
- the attribute
Rank 2: Process
thanks, as of now i am not storing the user id to any attribute
So how you know which document to which?
Rank 2: Process
you might be amaze as i am segregating the users data by permission
That's fine
But in your case I guess you'll need to add another field to be able to have a unique index that it's based on two attributes
Rank 2: Process
ok, i got your point thanks for your time,
Rank 2: Process
Thanks, this is working
Great
Rank 2: Process
using Appwrite DB or an external database like MariaDB which is better
Appwrite databse is indeed MariaDB
If you want and your project grows it might be better to decentraliz the MariaDB into a separate node or a managed one.
You can read a lot about it
https://discord.com/channels/564160730845151244/1097119647867863090