Envis10n

Yeah, I wasn’t trying to imply that it was a problem on the rust side or that they needed to name the keys that way, just that the JSON does need to have keys because that is how JSON works

I really like ORMs when they are well designed. With a bad API though, it hurts me to use them over a general query string.

I built a small driver for ArangoDB that just uses AQL behind the scenes because it’s so much easier to manage.

So, no. With the way you have it setup right now you would need to adjust your JSON structure to have the nation info be under a key, as well as the people array.

{
    "Nation": {...},
    "People": [...],
}

Every value has to have a key, unless it is the only value being serialized.

[1,2]

Is valid JSON, but

{ {"Id":1} }

Is not