Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a single calculated table for date template #639

Open
albertospelta opened this issue Apr 12, 2023 Discussed in #638 · 0 comments
Open

Use a single calculated table for date template #639

albertospelta opened this issue Apr 12, 2023 Discussed in #638 · 0 comments
Labels
area-ManageDates enhancement New feature or request
Milestone

Comments

@albertospelta
Copy link
Collaborator

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.

@albertospelta albertospelta added this to the vFuture milestone Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-ManageDates enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant