i.e. the document in the database is as it was presented. (Should be the same via the “Documents” page in the UI.)
However:
$ curl -su Administrator:password http://localhost:8093/query/service -d 'metrics=false&signature=false&pretty=true&statement=select d.* from default d use keys["example"]'
{
"requestID": "e4fae89c-6de5-472e-aab9-108917d08b89",
"results": [
{
"a": 3,
"b": 2,
"c": 1
}
],
"status": "success"
}
SQL++ (before MB-53938) alphabetises projection element names (and after still does for * expansions and nested fields).
HTH.
[edit] I should add, that my response in no way contradicts @mreiche’s - JSON doesn’t enforce field order hence the server is free to order as it sees fit.[/edit]