How do you prepare a funeral query for support or operation among parameters? Suppose that my processing has two fields field 1 & amp; Field2. How to design a URL to enable the following queries:
"Find the Myrrians where Field 1 = X or Field 2 = Y"
The design query in the rest is quite straight Are ahead, but do I have query fields between and only supported queries like / myresource? Field1 = x & amp; Field2 = y
with a free question might be to provide a single question parameter where the part, for example:
GET / myresource? Q = {field1 = x OR field2 = y}
But it will make it more complex for customers to parsing and enhancing or reducing the filtered areas.
What do you suggest?
query parameter definitions are not related, they are just inactive parameters - how do you handle them on Dependent or I recommend for search:
received / myresources? Field 1 = X and Field 2 = y & amp; Inclusive = true If you want to make the default for an AND relationship (proper), and you want that any other extension is definitely possible.
Comments
Post a Comment