Activity

Stefanel Pezamosca's activity

From 01/06/2025 to 02/04/2025

02:34 AM Database Feature #7020: always use "expanded" extent fields: I'm considering a solution: We could remove all references to denorm-extent and replace them with expanded-extents. T... Stefanel Pezamosca

09:30 AM Database Feature #7020 (Review): always use "expanded" extent fields: I have committed to 7020c revision 15690 some changes to address this:
>DDLGeneratorWorker$Helper.addField negates e... Stefanel Pezamosca
09:06 AM Database Feature #7020: always use "expanded" extent fields: Roger Borrello wrote:
> *No errors* in the build with @9537a-15672@. I was indicating that the previous attempts (wi... Stefanel Pezamosca
02:16 AM Database Feature #7020: always use "expanded" extent fields: Roger Borrello wrote:
> There are 2 builds of the customer application using @9537a-15672@, one as we have always bu... Stefanel Pezamosca

10:03 AM Database Feature #7020: always use "expanded" extent fields: Stefanel Pezamosca wrote:
> So, an update on 7020c, I was testing a customer application and encountered a regressio... Stefanel Pezamosca
07:09 AM Database Feature #7020 (WIP): always use "expanded" extent fields: So, an update on 7020c, I was testing a customer application and encountered a regression that seems to be related wi... Stefanel Pezamosca
07:08 AM Database Feature #7020: always use "expanded" extent fields: Roger Borrello wrote:
> Unfortunately, I ran out of space on my conversion attempt (see #7183-106). I will retry. Di... Stefanel Pezamosca

10:13 AM Database Feature #7020: always use "expanded" extent fields: I have rebased 7020c to trunk revision 15674.
I have committed a few fixes and code cleanup after the rebase and 70... Stefanel Pezamosca

08:13 AM Database Feature #7020: always use "expanded" extent fields: Hynek Cihlar wrote:
> Code review 7020c. The UI changes look OK to me.
>
> There are some files that are missing... Stefanel Pezamosca
07:34 AM Database Feature #7020 (Review): always use "expanded" extent fields: > There is one more issue I'm trying to fix related with expanded_extents=true. The fields that are empty strings are... Stefanel Pezamosca
03:59 AM Database Feature #7020: always use "expanded" extent fields: There is one more issue I'm trying to fix related with @expanded_extents=true@. The fields that are empty strings are... Stefanel Pezamosca

09:04 AM Database Feature #7020: always use "expanded" extent fields: I managed to fix some of the errors mentioned in #7020-62. There are more places in code that uses @PropertyMeta.getE... Stefanel Pezamosca
08:32 AM Database Feature #7020 (WIP): always use "expanded" extent fields: I realised that until now I tested with @denorm-extents=true@ configuration and not @expand-extents=true@.
I added @... Stefanel Pezamosca
05:30 AM Database Feature #7020 (Review): always use "expanded" extent fields: Ovidiu Maxiniuc wrote:
> * this is a very simple expression (only the @id_ext@ column), but the extent index can be ... Stefanel Pezamosca
02:27 AM Database Feature #7020: always use "expanded" extent fields: I have committed to 7020c revision 15669:
* Fixed inconsistency in frame widget handling when using denorm-extents.
... Stefanel Pezamosca

09:20 AM Database Feature #7020: always use "expanded" extent fields: I found a solution for the compilation issue:... Stefanel Pezamosca
04:14 AM Database Feature #7020: always use "expanded" extent fields: *Ovidiu*, I have the following testcases:... Stefanel Pezamosca

06:56 AM Database Feature #7020: always use "expanded" extent fields: I have rebased 7020c to trunk revision 15658 and it's now at revision 15668. I need to make sure that I didn't break ... Stefanel Pezamosca
05:04 AM Database Feature #7020: always use "expanded" extent fields: Firstly, I will try rebasing 7020c. If this fails, I will make a new 7020d branch and take the changes manually. Stefanel Pezamosca

06:32 AM Database Bug #9251 (Test): cache the translated FQL in FQLPreprocessor.translate: Branch 9251c was merged to trunk as rev. 15636 and archived. Stefanel Pezamosca
06:18 AM Database Bug #9251: cache the translated FQL in FQLPreprocessor.translate: Constantin Asofiei wrote:
> Stefanel Pezamosca wrote:
> > Considering that 9251c is fixing the regression mentioned... Stefanel Pezamosca

08:24 AM Database Bug #9251 (Internal Test): cache the translated FQL in FQLPreprocessor.translate: Considering that 9251c is fixing the regression mentioned and I also retested #9251-3 with similar results, I guess t... Stefanel Pezamosca

03:39 AM Database Bug #9251: cache the translated FQL in FQLPreprocessor.translate: Constantin Asofiei wrote:
> Please add javadoc for the new params for the ctors in @SortCacheKey@ and @TranslateCach... Stefanel Pezamosca
03:14 AM Database Bug #9251 (Review): cache the translated FQL in FQLPreprocessor.translate: I have created task branch 9251c from trunk revision 15630.
The patch is committed in revision 15631. Please review. Stefanel Pezamosca
03:07 AM Database Bug #9251 (WIP): cache the translated FQL in FQLPreprocessor.translate: As pointed out by Eduard [es], there seems to be a regression related with the addition of this cache:
> We cache th... Stefanel Pezamosca

Also available in: Atom