Virtual columns are a very good feature, but they impact the performance so heavily that we usually recommend to avoid it.
So, the idea here is to extend the virtual columns to manage just-UI columns - this would be rendered on demand, opposite to the actual virtual columns that are added on each query visiting the database.
Suggestion is to implement a notation in AD_Column.ColumnSQL to indicate that is UI virtual column (opposite to a normal DB virtual column). For example if the AD_Column.ColumnSQL starts with "@SQL=" - this indicates that is not a normal virtual column in database, but a virtual column that needs to be evaluated as a quick info - rendered using context.
Major
Virtual columns are a very good feature, but they impact the performance so heavily that we usually recommend to avoid it.
So, the idea here is to extend the virtual columns to manage just-UI columns - this would be rendered on demand, opposite to the actual virtual columns that are added on each query visiting the database.
Suggestion is to implement a notation in AD_Column.ColumnSQL to indicate that is UI virtual column (opposite to a normal DB virtual column).
For example if the AD_Column.ColumnSQL starts with "@SQL=" - this indicates that is not a normal virtual column in database, but a virtual column that needs to be evaluated as a quick info - rendered using context.