How to handle tsi data with multiple entities

[TechWatching]

I have tsi data that I would like to map to different classes because my events are of different "type/format" : all the same properties are not present on the events. And I want to avoid doing multiple requests to TSI.

I would like to do something like that :

var events = await environment.EventQuery<ITimeSeriesEntity>(FromDate, ToDate, Limit.Take, 200)
                    .ExecuteAsync();

where IEventQueryhas multiple implementation with different properties.

Is it something possible wtih Chronological ?

[colethecoder]

Chronological maps your query to a single C# type. I've run into the problem you are experiencing and solved it by having a type with multiple nullable properties to pull the data out in a single query. That is an ugly, hacky solution since you almost certainly then need to map your results to your desired models.

I suppose this is something you could resolve with a class containing collections of result types and some way of identifying your results as you processed them. Alternately it could use an abstract base type and a mechanism to determine which derived type to populate. Both have drawbacks and complexity, I don't intend on implementing either but if you wanted to propose a syntax and mechanism I'd be happy to review prior to you making a pull request.

[TechWatching]

Thanks for the quick answer. I was planning to have a type with nullable properties like you suggested, I just wanted to be sure that there was no other way already implemented in Chronological. So I guess I will try this way event if it's not a very nice solution as I unfortunately won't have time to implement a better solution.