Bad Performance on Query.SQL.Add
Posted: Fri 11 Jan 2019 12:01
Hi,
we have an realy huge code base with millions line of code and currently evaluating your components. Now we found an problem with very bad performance with multiple calls of SQL.Add with your query component.
It seems that every change from the sql statement results in parsing from the complete sql statement.
I know that it's possible to call SQL.BeginUpdate/SQL.EndUpdate ... I need the possibility to disable this behaviour and enable it on demand.
The ExpandMacro-method is not virtual so i have no chance to change this in my source code. It is possible to disable the parsing? Or it is possible to declare the ExpandMacro-method as virtual in your future builds?
Best regards
Manuel Bursch
we have an realy huge code base with millions line of code and currently evaluating your components. Now we found an problem with very bad performance with multiple calls of SQL.Add with your query component.
It seems that every change from the sql statement results in parsing from the complete sql statement.
I know that it's possible to call SQL.BeginUpdate/SQL.EndUpdate ... I need the possibility to disable this behaviour and enable it on demand.
The ExpandMacro-method is not virtual so i have no chance to change this in my source code. It is possible to disable the parsing? Or it is possible to declare the ExpandMacro-method as virtual in your future builds?
Best regards
Manuel Bursch