On 23/06/15 21:22, Laeeth Isharc wrote:
Thing is there are different use cases. For example, I pull data from Quandl - the metadata is standard and won't change in format often; but the data for a particular series will. For example if I pull volatility data that will have different fields to price or economic data. And I don't know beforehand the total set of possibilities. This must be quite a common use case, and indeed I just hit another one recently with a poorly-documented internal corporate database for securities.
If the data can change between calls or is not consistent my serialization library is not a good fit. But if the data is consistent but changes over time, something like once a month, my serialization library could work if you update the data structures when the data changes.
My serialization library can also work with optional fields if custom serialization is used.
-- /Jacob Carlborg
