Focused Query
World is a complex place, and business rules are usually over complicated, inherited, personalized
and opinionated client view of their business. Some would say that "This is the way
".
To navigate throught this data jungle EYWA provides set of tools and one of these tools is search query as mentioned. Is the force strong with search query? Indeed force is strong with this one. As mentioned ordering can be combined on multiple levels, but so can query parameters. What does this meen?
EYWA search queries can be focused on any level of selection for any attribute as well as
with initial query parameters in query itself. "This is one ugly bastard.
"
#
Search Operator Example{ searchDataset (_order_by:[{name:asc}]) { name versions(_where:{deployed:{_eq:true}}) { name entities (_order_by:[{name:desc}]) { name attributes(_where:{name:{_eq:"Active"}}) { name type } } } }}
#
Response{ "data": { "searchDataset": [ { "name": "Authentication, Authorization & Access", "versions": [ { "name": "1", "entities": [ { "name": "User Role", "attributes": [ { "name": "Active", "type": "boolean" } ] }, { "name": "User Group", "attributes": [ { "name": "Active", "type": "boolean" } ] }, { "name": "User", "attributes": [ { "name": "Active", "type": "boolean" } ] } ] } ] }, { "name": "Datasets", "versions": [ { "name": "1", "entities": [ { "name": "Dataset Entity Attribute", "attributes": [ { "name": "Active", "type": "boolean" } ] } ] } ] } ] }}