Change on query object schema about franca-js HOT 3 OPEN

Since the write needs the type, query and option sometime, it's very confusing if we still allow type to be placed in the top level of query object. We should just put the type in the query, insert or update, they can specify the type just for query or write.

I see what you're saying. I'd like type as a top level key for simple queries that are query only. So this would be a valid query:

{
  "type": "STANDARD",
  "field": "name",
  "match": "Bob"
}

The type here shouldn't really apply to writes, since values for type are things like AND and OR.

If anything, writes should have their own types, values being INSERT, UPDATE, and RAW. Does that sound reasonable?

from franca-js.

@chen-factual I see, so the reason I think keeping type at the top level might be confusing because we may assign different types for query and write(like update), for instance:

{
  "type": "RAW",
  "table": "example-table",
  "query": {
    "field": "field1",
    "match": "baz"
  },
  "upsert": {
    "$set": {
      "field2": "boo",
      "field3": "bar"
    },
    "$setOnInsert": {
      "field1": "baz",
      "field2": "boo",
      "field3": "bar"
    }
  }
}

So in this case, upsert is raw but query is just a standard query. Do you think we need this kind of query object in practice?

from franca-js.

I can see a corner use case for it, but in the interest of simplifying things I'd be glad if we enforce RAW to apply to everything, instead of selectively to just one or the other.

from franca-js.