FWD » Core Development » Database

10/29/2020

12:11 PM Feature #4055: optimize temp-table output parameter copying

I will ignore #4055-60 for now, it doesn't fit my understanding of how @copy-temp-table@ is working. I will document ... Adrian Lungu

07:06 AM Feature #4055: optimize temp-table output parameter copying

I am a bit confused of two recently generated testcases. I tried to experiment with @copy-temp-table@ in the context ... Adrian Lungu

05:34 AM Feature #4055: optimize temp-table output parameter copying

Eric Faulhaber wrote:
> Each legacy temp-table index, whether it is unique or not in the legacy schema, is created w... Adrian Lungu

10/28/2020

02:02 PM Feature #4055: optimize temp-table output parameter copying

Insofar as this affects your design decisions, please note that we do not actually create unique indices for temp-tab... Eric Faulhaber

10/27/2020

08:42 AM Feature #4055: optimize temp-table output parameter copying

I have experimented some scenarios both in 4GL and FWD and I wanted to point out some hot-spots and maybe some optimi... Adrian Lungu

10/26/2020

09:46 AM Feature #1587: implement full support for word indexes

Creates task branch 1587a
Igor Skornyakov

10/23/2020

11:22 AM Feature #4980 (New): Investigate the impact of TOAST manipulation in PotgreSQL engine

PostgreSQL has a manager (named TOAST) which ensures that all texts wider than TOAST_TUPLE_THRESHOLD (usually 2kB) ar... Adrian Lungu

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. Constantin Asofiei

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 ... Eric Faulhaber

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... Adrian Lungu

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 ... Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

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... Eric Faulhaber

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... Ovidiu Maxiniuc

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? Eric Faulhaber

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;... Ovidiu Maxiniuc

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 ... Constantin Asofiei

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 ... Constantin Asofiei

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... Eric Faulhaber

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... Ovidiu Maxiniuc

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... Eric Faulhaber

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:
... Ovidiu Maxiniuc

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... Eric Faulhaber

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... Eric Faulhaber

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... Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

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... Eric Faulhaber

12:25 PM Bug #4945: Optimize indexes for H2 dialect

What happens if the index in 4GL is originally as @index ix1 f1 desc@? Constantin Asofiei

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... Ovidiu Maxiniuc

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... Constantin Asofiei

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... Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

10:48 AM Bug #4945 (Feedback): Optimize indexes for H2 dialect

Ovidiu Maxiniuc

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 ... Igor Skornyakov

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... Greg Shah

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. ... Ovidiu Maxiniuc

09:10 AM Bug #4940 (New): Refactor the overlapping DmoMeta, RecordMeta, and PropertyMeta classes into a mo...

Ovidiu Maxiniuc

07:22 AM Bug #4926 (Closed): "guest already exists with ? ?. (132)" error in Hotel GUI

Greg Shah

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.... Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

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... Eric Faulhaber

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. Ovidiu Maxiniuc

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... Ovidiu Maxiniuc

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... Eric Faulhaber

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... Ovidiu Maxiniuc

12:52 PM Bug #4926: "guest already exists with ? ?. (132)" error in Hotel GUI

The issue is fixed in 3821c/r11641. Ovidiu Maxiniuc