firebird-automations

Commented by: Sean Leyne (seanleyne) My reading of this case is that this issue can be closed, since there is no new action/change which is required\. Correct?

Commented by: @dyemanov I'm not sure\. Some benefits of this feature still exist, the question is primarily whether they justify the development cost\. But regardless, the priority should be decreased...

Commented by: @livius2 If you still need real world sample: table REPORT with column STATE \(something like Firebird Tracker\) values of state: closed \- common value e\.g\. 1000000 records open...

Commented by: @livius2 If this feature will be done and it can be then used in referential constraints, then benefit will be much bigger Example \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- instead of tables NOTES\_CUSTOMER,...

Modified by: @pavel-zotov description: DDL: #⁠#⁠#⁠#⁠ create or alter procedure null\_arg\_force\_idx\_usage as begin end; create or alter procedure null\_arg\_optimization\_test\_01 as begin end; create or alter procedure null\_arg\_optimization\_test\_02 as begin end;...

Modified by: @pavel-zotov summary: OR'ed optimization in 3\.0 is ineffective when \`WHERE\` clause contains two expression and they do NOT match order of SP input arguments =\> OR'ed optimization in...

Modified by: @dyemanov assignee: Dmitry Yemanov \[ dimitr \]

Modified by: @dyemanov Regression: 3\.0 Alpha 2 \[ 10560 \]

Commented by: @dyemanov I've corrected the ticket title as it has nothing to do with order of SP parameters, only order of predicates inside WHERE matters here\. The issue is...

Modified by: @dyemanov Component: Engine \[ 10000 \] summary: OR'ed optimization in 3\.0 is ineffective if WHERE\-clause contains two expression and they do NOT match to order of SP input...