You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by bdarbonneau April 11, 2023
When Bravo creates a calendar table, it creates a hidden calculated table, then another one that refers to the first one. The model eventually contains two identical tables, one of them not used but which still consumes memory. Why not create a single one ?
I am curious to understand the reason behind this design choice.
The text was updated successfully, but these errors were encountered:
Discussed in #638
Originally posted by bdarbonneau April 11, 2023
When Bravo creates a calendar table, it creates a hidden calculated table, then another one that refers to the first one. The model eventually contains two identical tables, one of them not used but which still consumes memory. Why not create a single one ?
I am curious to understand the reason behind this design choice.
The text was updated successfully, but these errors were encountered: