-
Notifications
You must be signed in to change notification settings - Fork 55
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
Save Derived Column values to PropertyState #3438
Comments
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This will be addressed through #3430 |
#3430 is closed but the issue remains. reopening this one |
I really like this idea. The fact it mirrors extra data so closely really does us a favor. I'm going to start documenting where logic needs to be added. To be updated. Add column to
|
Some notes on use case:
@haneslinger will do some benchmarking on a large db to see how 'expensive' caching the fields and recalculating them will be. |
right-o, ive done some benchmarking
|
let's await the import performance updates and revisit this issue! |
Background
Derived Columns are loosely calculated as:
derived_column_value = derived_column.evaluate(property_state)
Issue
Derived Column values are dynamically calculated on each inventory list page load and have a few known performance issues:
Saving derived column data to the database would increase performance and allow for more advanced filtering and sorting.
A potential solution:
derived_data
. This would be similar to 'extra_data' on the property_stateThe text was updated successfully, but these errors were encountered: