#[SOLVED] Send Array of object in document attribute?

8 messages · Page 1 of 1 (latest)

dusky solar
#

how do you send array of objects to the document or how do you set it up?
Like this,
[
{
name:'abc',
age:12
}
]

austere zealot
dusky solar
#

yeah. But if we need to have 1 documents per user and have all the data associated to that user in one document. Then how do we achieve that?

Lets assume I am writing a blog, I need to have a document listing all of my blogs as array of objects.
if 2nd user logs in to the system, he should have the document of his blog posts. So that we can fetch it all at once.

fiery roost
#

This is unconventional, esp in light of what I posted in #🏠│general about having to specify max string length in whatever field you want to store your array. You might want to consider storing one document per blog, and setting document-level permissions on that blog so only the user can get their own blogs. That way you can simply run a Query on the collection to get all blogs from one user

dusky solar
#

So it means, Each document will be a separate blog object, with a unique identifier being lets say user-id. And I will have to query it based on that userID

austere zealot
fiery roost
#

Not quite. Store each blog post as a separate document with its own unique id - not the users. When saving a post, set the permissions for that user using Role.user([USER_ID]). Then use the Query class to query the collection. By default, since that user only has permissions to get their own documents, you'll get an array of documents from the Query response that contains all and only that one users records. You can of course store EACH blog post with the users id as an attribute and then query for that attribute to use that users id as a filter .... but unless you're reading these on the server, you'll still want to set document-level permissions on that collection. https://appwrite.io/docs/permissions

Appwrite

Appwrite provides web and mobile developers with a set of easy-to-use and integrate REST APIs to manage their core backend needs.

dusky solar
#

Interesting. Now it makes sense. Thanks for the response.