@nilan Per the above discussion, are JSON fields non-queryable?

@dk0r JSON fields are indeed queryable. I wonder why you want to model first name, last name etc as a list of Strings rather than separate String fields. What benefit are you hoping to get out of this?

@nilan, I'm new to backend and databases and it just seemed more orderly to have an object containing related info (names, address, dateofBirth, etc) rather than having serparate fields for each

I'd advice for using separate fields instead. Sometimes you are interested in JUST the street name, or JUST the city, and not the complete address

and then just create a user => address relation?

exactly, a one-to-one relation most probably

@agartha btw, apparently json objects are queryable ^

I think it's a terminology thing. To put it more clearly:

@dk0r I explained what I meant by queryable

- json fields can be returned to the client by including them in the GraphQL query (as you would expect) - no filters exist for json fields. you cannot query all items that have a certain json property key/value in one of their fields

With queryable, I meant can be used for filtering, ordering, etc. [22:58] they will show up in query results of course [22:59] If you want to query a list of users ordered by last name, and last name is part of a JSON field, you can't do that

what's a practical/common use case for a json field?

a typical use case is to store data whose structure is not necessarily known beforehand or differs between different nodes

I use it for two things mostly: user defined fields (use case 1), and payload for my message queue Type (use case 2).