4 ms·
That is actually good in my opinion, because of how static records are expected to be in structure. You shouldn't be able to reload or proceed with data dating
by mononcqc 13y ago
That is actually good in my opinion, because of how static records are expected to be in structure. You shouldn't be able to reload or proceed with data dating from an earlier version as if nothing happened.
You have to think about what changed and prepare for an upgrade from any version you may encounter, rather than move along with incorrect data, similar to if it were corrupted.
I fear Erlang programmers will use maps in a way that allows them to be sloppy, rather than just exploiting the flexibility they allow. Double-edged sword, in a way.
- gordonguthrie 13y agoI suspect what you will find is that API's are defined with records, one or more of whose fields is a map. You do kind of do that with Mnesia tables where you want to specify the indexable-keys up front, but need to have the flexibility to extend the schema - a nice kv list does the trick.