Hi all, I have been playing around with the session API and have been stumbling into some pits, that I think would be worth addressing.
The biggest issue I have had recently is using the executeAggregationQuery method, passing in pairs of queries and aggregations. However, I noticed that if for example I pass in 3 queries with the middle one being invalid, that I simply get back a 2-field response and I have no way of seeing which field was invalid. In general, I think the passing in multiple lists with each the same size sort of feels a bit odd. Instead of passing in one list of objects which again have multiple options would be a preferrable approach. Also, would this allow us to add these as references to the responses. So having a Field returned by RowRecord.getFields() have a reference to the query object, would make the API better to handle. We wouldn’t have to pass the fields when returning the result, this could be something the client does completely in the client to avoid unnecessary payload. I do think however for this to work, that we would need some sort of error handling, passing back something like an ErrorField, if a query was wrong or anything similar. Chris
