Reduce amount of used ets
tables
#123
Labels
enhancement
Improvement of existing functionality or request of improvement
internal API
Anything related to the internal API and implementations
In the current situation, the number of
ets
tables is proportional to the number of schemas. Every time we parse nested schema we create a newets
schema that goes into recursion.Despite that fact we already have a cache on top of the schema resolution which is a single place for all schemas after they are resolved we don't leverage it.
It will allow us to reduce coding in related issue #115
TODO
ets
tables #124The text was updated successfully, but these errors were encountered: