Activity
From 10/13/2020 to 11/11/2020
11/12/2020
- 09:05 PM Feature #4996: Integrate hash indexes in H2 temp-tables
- IMHO, we can not benefit much from the hash indexes. The way I understand the H2 documentation (@H2 Performance@ / @I...
11/11/2020
- 05:19 PM Feature #4996: Integrate hash indexes in H2 temp-tables
- Sorry, I re-read your post and it seems I had misread your conclusion on my first pass. Nevertheless, I expect we wou...
- 03:01 PM Feature #4996: Integrate hash indexes in H2 temp-tables
- Adrian Lungu wrote:
> In H2, if the where clause contains a @_multiplex@ equality, than this index with have a ver...
11/10/2020
- 07:10 AM Feature #5003: Enhance performance of H2 sequences
- There is a @Sequence.DEFAULT_CACHE_SIZE@ which defaults on 32. This refers to how often the sequence is flushed (and ...
- 07:08 AM Feature #5003 (WIP): Enhance performance of H2 sequences
- 06:49 AM Feature #3574 (WIP): finish implementation of temp-table XML support
- From Ovidiu:
> Here are the remaining known issues:
>
> * At this moment I am trying to find a solution for the ... - 06:47 AM Feature #4397 (Test): add database attrs, methods and options
- 02:48 AM Feature #1587: implement full support for word indexes
- Ovidiu Maxiniuc wrote:
> I did a quick research and it looks like the H2 does not have any limitations related to ma... - 07:57 PM Feature #1587: implement full support for word indexes
- I did a quick research and it looks like the H2 does not have any limitations related to maximum identifier length (t...
11/07/2020
- 03:08 AM Feature #1587: implement full support for word indexes
- Ovidiu Maxiniuc wrote:
> Are these helper tables specific to a table we already have? You might add a specific suffi...
11/06/2020
- 04:26 PM Feature #1587: implement full support for word indexes
- Are these helper tables specific to a table we already have? You might add a specific suffix, following the normalize...
- 03:39 PM Feature #1587: implement full support for word indexes
- A strange question. We need to generate unique names for the word tables. I would prefer to have them more or less me...
- 03:29 PM Feature #1587: implement full support for word indexes
- Ovidiu Maxiniuc wrote:
> Igor, here is a how I would tackle this issue.
> First, I would create a simple testcase l... - 03:08 PM Feature #1587: implement full support for word indexes
- Igor, here is a how I would tackle this issue.
First, I would create a simple testcase like:... - 02:27 PM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> My question was about whether we needed to refactor the conversion of ABL WHERE clauses t... - 02:14 PM Feature #1587: implement full support for word indexes
- Igor Skornyakov wrote:
> Greg Shah wrote:
> > Perhaps it is better to avoid changes at conversion time and instead ... - 01:44 PM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> Perhaps it is better to avoid changes at conversion time and instead to implement the rewriting a... - 01:41 PM Feature #1587: implement full support for word indexes
- Perhaps it is better to avoid changes at conversion time and instead to implement the rewriting at runtime. This wou...
- 01:33 PM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> Currently, we convert the ABL WHERE clause to FQL which uses the CONTAINS UDF. Is there any ... - 12:55 PM Feature #1587: implement full support for word indexes
- Currently, we convert the ABL WHERE clause to FQL which uses the CONTAINS UDF. Is there any reason to refactor this? ...
- 11:20 AM Feature #1587: implement full support for word indexes
- Thank you. I will start with the conversion of the logical expression (in a format required by the @CONTAINS@ operato...
- 11:02 AM Feature #1587 (WIP): implement full support for word indexes
- Considering that you think it will take around a week, please go ahead with your proposed solution, Igor. Thanks.
- 10:53 AM Feature #1587: implement full support for word indexes
- Well, it looks that FTS support in PostgreSQL is flexible enough and it will be possible to use it for @CONTAINS@ sup...
- 10:37 AM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> What is your estimate of the time needed to implement your proposed solution? If it is small eno... - 10:14 AM Feature #1587: implement full support for word indexes
- What is your estimate of the time needed to implement your proposed solution? If it is small enough, then it may mak...
- 04:22 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> That being said, before we go this route, I'd like to know if we are ignoring something whic... - 12:02 AM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> The specific solution does not matter to me so long as it is compatible and fast. Anything (Igor... - 04:31 AM Feature #4996: Integrate hash indexes in H2 temp-tables
- The goal of this task is to explore hash index potential uses for the H2 temp-tables. For example, this can boost the...
11/05/2020
- 10:02 AM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> As of this moment, we don't need to implement our own word break tables. We can avoid this featu... - 09:53 AM Feature #1587: implement full support for word indexes
- I like this Russian saying "shooting a canon at sparrows".
As of this moment, we don't need to implement our own w... - 09:44 AM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> > I have no experience with full-text search support in SQL databases, but after a quick look at ... - 09:14 AM Feature #1587: implement full support for word indexes
- The specific solution does not matter to me so long as it is compatible and fast. Anything (Igor's idea or the built...
- 09:13 AM Feature #1587: implement full support for word indexes
- > I have no experience with full-text search support in SQL databases, but after a quick look at the documentation, I...
- 08:15 AM Feature #1587: implement full support for word indexes
- Greg Shah wrote:
> Some useful references:
>
> * "ElasticSearch":https://en.wikipedia.org/wiki/Elasticsearch - th...
11/04/2020
- 12:43 PM Feature #4996 (WIP): Integrate hash indexes in H2 temp-tables
- 09:24 AM Bug #4994: NPE in AdaptiveQuery when loading null data for an outer join
- When a @CompoundQuery@ has a component using the OUTER JOIN option, we try to load data via the @AdaptiveQuery.load(O...
- 09:13 AM Bug #4994 (Closed): NPE in AdaptiveQuery when loading null data for an outer join
- 03:53 AM Feature #4055: optimize temp-table output parameter copying
- Regarding @optimize extent bulk copy using insert into select from@, I found an optimization which doesn't rely anymo...
10/30/2020
- 01:14 PM Feature #1587: implement full support for word indexes
- The @TEMP-TABLE:ADD-NEW-INDEX@ method depends on this, as noted in #4397. When task is finished, the word indexes mus...
- 01:05 PM Feature #4397: add database attrs, methods and options
- >> TEMP-TABLE:ADD-NEW-INDEX() method
>
> Not touched. (It is currently marked as partial because it doesn't handle ... - 11:53 AM Feature #4397: add database attrs, methods and options
- Status of issues in 4397a/11776.
> * @BUFFER:LAST-BATCH@ attribute
Done 99%. There is one edge-case where a "look-a... - 07:12 AM Feature #4055: optimize temp-table output parameter copying
- Directions for temp-table copy optimization:
* -extend the use of *insert into select from* for some cases of append... - 07:08 AM Feature #4055: optimize temp-table output parameter copying
- *Extent*: When in @insertBulk@ mode, the extents fields are copied one by one. This can be also optimized with a @in...
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 ...
- 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 ...
- 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...
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...
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...
10/26/2020
- 09:46 AM Feature #1587: implement full support for word indexes
- Creates task branch 1587a
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...
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 ...
Also available in: Atom