3 ms·
normalizing from raw json isn't terribly complicated but it's definitely more complicated than just indexing some paths into it. if the json is loosely defined
by gfody 4y ago
normalizing from raw json isn't terribly complicated but it's definitely more complicated than just indexing some paths into it. if the json is loosely defined normalization might not be practical (ie requiring too many tables or needing to be revisited too frequently as the json format evolves too often, etc, etc.)
- tracker1 4y agoThe example I like to give is different payment types... CC/Payflow, Paypal, Amazon Checkout, etc... all you really care about is the type and amount and success... The additional details, different transaction id's etc are different... this allows one to use a single field for the "extra" details, while normalizing a few bits that may come back from different services in a different way, but a single type of collective data. Normalizing the above would mean at least 4 tables, with subqueries and joins that really aren't valueable at the database layer.