perf: Ignore is_opening column in GL Queries (backport #45327) #45785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is Opening
column allows users to add opening entries irrespective of posting date and fiscal year.This should not ideally be allowed after the balance sheet is frozen for the first fiscal year in the system.
This column is used in all queries for getting opening balance, one more side effect this column has is since the posting date can be any date, the tables cannot be logically partitioned based on the posting date to make queries efficient. Once the user reaches large volume of data in GL Entry, these queries take a lot of time to execute and sometimes more than the report timeout limit.
Added a check to ignore this column in queries, once the user has imported all opening entries with posting date before the date system actually came to use with live entries, this column becomes irrelevant.
This is an automatic backport of pull request #45327 done by [Mergify](https://mergify.com).