Activity
From 09/22/2020 to 10/21/2020
10/20/2020
- 01:21 PM Bug #4825: OutputTableHandleCopier dynamically defines destination temp-table
- Attached is the patch which instruments the @OutputTableHandleCopier.finished@ method via JMX bean.
10/19/2020
- 04:29 PM Bug #4825: OutputTableHandleCopier dynamically defines destination temp-table
- Eric Faulhaber wrote:
> A useful first step to help prioritize this optimization would be to instrument this code ...
10/15/2020
- 02:50 AM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu, there is no H2 dedicated repository yet. My patch on H2 is not safe, so I didn't worry about a repository jut...
10/14/2020
- 07:12 PM Bug #4945: Optimize indexes for H2 dialect
- I finished the solution for avoiding re-sorting the data if a reversed index is detected. I have chosen the solution ...
10/09/2020
- 05:20 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> OK, as soon as you are comfortable with your FWD-only changes, please commit them.
Done, se... - 04:40 PM Bug #4945: Optimize indexes for H2 dialect
- OK, as soon as you are comfortable with your FWD-only changes, please commit them.
As to the H2 changes, please DO... - 04:27 PM Bug #4945: Optimize indexes for H2 dialect
- I will answer in reverse order.
> Is the first item in #4945-15 something that stands on its own?
Yes, I adjusted... - 03:53 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu, do you expect to have any update today? Is the first item in #4945-15 something that stands on its own?
10/08/2020
- 06:36 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> Without the @_multiplex@ first at the ORDER BY, the WHERE will choose a different index;...
10/07/2020
- 01:43 AM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> Constantin, do you remember why we moved @_multiplex@ to the front of index definitions and ... - 01:40 AM Bug #4945: Optimize indexes for H2 dialect
- From my debugging of the AdaptiveQuery, in H2 the LIMIT is applied at the fetch, and not after re-sort, if the fetch ...
10/06/2020
- 05:40 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > Are you talking about H2 changes here, or just FWD changes?
> T... - 05:27 PM Bug #4945: Optimize indexes for H2 dialect
- When H2 selects the index @Select.getSortIndex()@ it looks for the first N components of the index to be a perfect ma...
- 05:03 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin, do you remember why we moved @_multiplex@ to the front of index definitions and ORDER BY clauses? I origi...
- 05:00 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> Are you talking about H2 changes here, or just FWD changes?
There are two set of changes:
... - 04:17 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > But will this mean H2 will select the index AND not re-sort afte... - 03:36 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > What happens if the index in 4GL is originally as @index ix1... - 01:20 PM Bug #4945: Optimize indexes for H2 dialect
- Another issue I noticed while debugging: there was an extra index, having the @recid@ as unique component. It was mar...
- 01:11 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> But will this mean H2 will select the index AND not re-sort after the results are fetched? O... - 01:07 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> What happens if the index in 4GL is originally as @index ix1 f1 desc@?
Evidently, the... - 12:27 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Right. I am adding now the @DESC@ direction to @_multiplex@ when FWD detects a reversed i... - 12:25 PM Bug #4945: Optimize indexes for H2 dialect
- What happens if the index in 4GL is originally as @index ix1 f1 desc@?
- 12:24 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> I don't understand - what's the exact @ORDER BY@ clause? Do you mean there is an @ORDER... - 12:13 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> * I discovered a bug in FWD related to sorting temp-tables queries. When a reversed order i... - 11:18 AM Bug #4945: Optimize indexes for H2 dialect
- I took a look over H2 code that handles selection of the index (@Select.prepare()@)to be used for a query and the pos...
- 10:54 AM Bug #4945: Optimize indexes for H2 dialect
- We notice that sometimes the temp-table queries are slow because the matching reversed index is not selected by the q...
- 10:48 AM Bug #4945 (Feedback): Optimize indexes for H2 dialect
10/05/2020
- 12:33 PM Feature #3814: more schema metadata
- Greg Shah wrote:
> Igor: Are @_area@, @_filelist@ and @_tenant@ all "complete" (stubbed out with a basic functional ... - 12:01 PM Feature #3814: more schema metadata
- Igor: Are @_area@, @_filelist@ and @_tenant@ all "complete" (stubbed out with a basic functional set of constant data...
10/02/2020
- 09:22 AM Bug #4940: Refactor the overlapping DmoMeta, RecordMeta, and PropertyMeta classes into a more rat...
- The @DmoMeta@, @RecordMeta@, and @PropertyMeta@ do overlap in some measure. They need to be refactored / simplified. ...
- 09:10 AM Bug #4940 (New): Refactor the overlapping DmoMeta, RecordMeta, and PropertyMeta classes into a mo...
- 07:22 AM Bug #4926 (Closed): "guest already exists with ? ?. (132)" error in Hotel GUI
10/01/2020
- 01:16 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- I did not observe any regressions while testing hotel_gui and customer application so I decided to commit the update....
- 12:10 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- I do not see any issues with customer code.
The query that was exceeding 150ms is no more present in my statistics b... - 11:54 AM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- Ovidiu Maxiniuc wrote:
> I did not log any of this activity. I am thinking of doing it.
If you mean permanent log... - 11:45 AM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- I did not log any of this activity. I am thinking of doing it.
- 11:44 AM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- I did not make any test regarding this, but it should work.
If we have @A.a1 = B.b1@ as join relation, the logic tha... - 11:33 AM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- Ovidiu Maxiniuc wrote:
> I attached the patch, if you have time, please review. If everything is fine, I will push... - 10:38 AM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- Eric,
I have an implementation which is quite stable for my test-case. I am putting it to the test against hotel_gui... - 12:52 PM Bug #4926: "guest already exists with ? ?. (132)" error in Hotel GUI
- The issue is fixed in 3821c/r11641.
09/29/2020
- 12:51 PM Bug #4931: possible ProgressiveResults performance improvement
- @AdaptiveQuery@ uses @ProgressiveResults@ internally to fetch a progressively larger set of query results. The origin...
- 12:30 PM Bug #4931 (New): possible ProgressiveResults performance improvement
- 10:57 AM Support #4928: rewrite FieldReference to use lambdas instead of reflection
- At runtime we generate implementation classes to back the DMO interfaces. All of these classes have existing methods...
- 09:49 AM Support #4928 (New): rewrite FieldReference to use lambdas instead of reflection
- 12:43 AM Bug #4926: "guest already exists with ? ?. (132)" error in Hotel GUI
- Conversation via email:
---
>> Ovidiu Maxiniuc wrote:
>>>
>>> I am investigating the ** guest already exists ... - 11:57 PM Bug #4926 (Closed): "guest already exists with ? ?. (132)" error in Hotel GUI
09/27/2020
- 04:09 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- This fix is intended only for the case where we have sort clauses for more than one table concatenated together, and ...
- 03:52 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- Something to share about my investigations with H2 - if the chosen index didn't match the ORDER BY clause, then H2 wi...
- 03:15 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- I initially thought there would be an @AbstractJoin@ object in the second query component we could use to analyze the...
- 03:08 PM Bug #4917: eliminate redundant ORDER BY elements in multi-table queries
- We have found that in certain cases (e.g., optimized @CompoundQuery@), multi-table queries are generated with ORDER B...
- 02:55 PM Bug #4917 (New): eliminate redundant ORDER BY elements in multi-table queries
09/25/2020
- 07:09 AM Feature #4055: optimize temp-table output parameter copying
- Adrian Lungu wrote:
> Unfortunately, almost every member of @RecordBuffer@ should be retrieved through getters in or... - 06:38 AM Feature #4055: optimize temp-table output parameter copying
- Constantin, the testcases work now. Unfortunately, almost every member of @RecordBuffer@ should be retrieved through ...
09/24/2020
- 01:59 PM Feature #4055: optimize temp-table output parameter copying
- Adrian, I've backed out my ArgumentBuffer change in 3821c rev 11577 - the solution was to use getters for RecordBuffe...
- 08:24 AM Feature #4055: optimize temp-table output parameter copying
- Ovidiu Maxiniuc wrote:
> Review of 3821c rev 11565.
>
> The code looks good to me. I cannot say I fully get all o...
09/23/2020
- 07:48 PM Feature #4055: optimize temp-table output parameter copying
- Review of 3821c rev 11565.
The code looks good to me. I cannot say I fully get all of it but I did a double pass o... - 06:36 AM Feature #4055: optimize temp-table output parameter copying
- Adrian, thanks for the explanation. We can't make the @buffer()@ and @definition()@ methods non-final, as this will ...
- 05:01 AM Feature #4055: optimize temp-table output parameter copying
- Constantin, the @RecordBuffer$ArgumentBuffer@ seems to be broken - the use of parameter buffers in queries was result...
09/22/2020
- 06:33 PM Feature #4055: optimize temp-table output parameter copying
- 3821c rev 11565 contains another pass at improving the 'field-by-field' copy. @RecordBuffer$DatumAccess@ was enhance...
Also available in: Atom