Activity
From 01/15/2025 to 02/13/2025
02/13/2025
- 10:54 AM Feature #6720: lazy hydration
- Committed @6720b/15700@ with the the implementation to hydrate all the unhydrated fields when the session closes.
... - 07:16 AM Feature #6720: lazy hydration
- > Regarding, the idea to fully hydrate the records that are still loaded when the session closes. I also like it, I c...
- 06:21 AM Feature #6720: lazy hydration
- So, I have tried the example from the last note where I closed the session before the commit in debugger. As a result...
- 04:08 AM Feature #6720: lazy hydration
- Agree with #6720-80. Doing updates will keep the session open as long as the transaction is open. If there is no tran...
- 02:53 AM Feature #6720: lazy hydration
- Yesterday, I had a discussion with Alex, mainly focused on 2 things:
# Should the session really be closed when exit... - 09:48 AM Feature #7020: always use "expanded" extent fields
- I did some other small changes and *7020c* is now at revision *15707*.
With denorm-extent the name of the word tab... - 06:00 AM Bug #9590: Double LOAD for each record in FWD
- Committed *9590a/15680*. Avoid double firing of a FIND trigger when the DynamicResults use a RandomAccessQuery query....
- 03:55 AM Bug #9590: Double LOAD for each record in FWD
- The fix from #9590-22 is good for DynamicResults, but not ScrollingResults. We rely on the already parsed results and...
- 02:27 AM Bug #9633: bulk delete for permanent tables
- Eric Faulhaber wrote:
> Alexandru Lungu wrote:
> > We have the bulk delete for temporary tables, maybe that can be ...
02/12/2025
- 09:26 AM Bug #9633: bulk delete for permanent tables
- Alexandru Lungu wrote:
> We have the bulk delete for temporary tables, maybe that can be used as a source of inspira... - 08:50 AM Bug #9633: bulk delete for permanent tables
- We have the bulk delete for temporary tables, maybe that can be used as a source of inspiration.
- 08:47 AM Bug #9633: bulk delete for permanent tables
- Another note: we should always force an outer tx when we do the bulk delete. Because the code like @for each book ex...
- 09:18 AM Feature #6720: lazy hydration
- I currently have this change to @Hydrator.java@:...
- 07:27 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- 9317a/15689 passed the MT harness test ✅.
02/11/2025
- 09:47 AM Feature #9456 (WIP): implement SQL Server dialect and helpers
- I set up a MSSQL instance for a new customer and put to the test the DDLs FWD generates today. I know for sure a few ...
- 05:08 AM Bug #9633: bulk delete for permanent tables
- I want to stress that the run-time is there, but may be flawed considering it was dead-code by now. Some part is comm...
- 03:25 AM Bug #9633: bulk delete for permanent tables
- FWD emits bulk delete aka @deleteForAll@ only for temp-tables. We need to emit these also for permanent tables. The...
- 03:22 AM Bug #9633 (Review): bulk delete for permanent tables
02/10/2025
- 06:04 AM Feature #6720: lazy hydration
- > In 6720b, the records also have their hydrator refreshed. With your example, I would like to find out why the code ...
- 05:00 AM Feature #6720: lazy hydration
- > Currently, as I think the session should indeed be closed in this case, the solution is to catch the LazyHydrationE...
- 03:36 AM Feature #6720: lazy hydration
- Currently, as I think the session should indeed be closed in this case, the solution is to catch the @LazyHydrationEx...
- 02:54 AM Feature #6720: lazy hydration
- During regression testing of a large customer application I found some problems. Most of them have a @LazyHydrationEx...
02/07/2025
- 08:24 AM Feature #9623: honoring database users and database-defined access control
- OE has features that allow customers to:
# Define users at the database (the @_user@ table). *There is no group s... - 08:13 AM Feature #9623 (New): honoring database users and database-defined access control
- 06:34 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Committed on the testcases project, rev. 1704 the 10 new 4GL unit tests. These verify the number of results and the o...
- 04:19 AM Feature #7020 (Review): always use "expanded" extent fields
- 7020c was rebase to trunk revision 15687.
I have committed 15704/15705, please review:
Removed support for denorm...
02/06/2025
- 04:24 PM Feature #9544: implement missing SESSION handle attributes
- Greg Shah wrote:
> Code Review Task Branch 9544a Revision 15688
>
> No objections. The reporting changes only ne... - 11:16 AM Feature #9544 (Internal Test): implement missing SESSION handle attributes
- 11:15 AM Feature #9544: implement missing SESSION handle attributes
- Code Review Task Branch 9544a Revision 15688
No objections. The reporting changes only need simple testing with H... - 07:59 AM Feature #9544 (WIP): implement missing SESSION handle attributes
- I created branch 9544a and committed the updates on gap info for @FIRST-BUFFER@ and @FIRST-QUERY@ @SESSION@ attributes.
- 11:18 AM Feature #9542 (Review): finish ORIGIN-HANDLE ProDataSet attribute
- Code Review Task Branch 9544a Revision 15689
I saw the changes from this task were added to 9544a.
I see no iss... - 10:25 AM Feature #6720: lazy hydration
- *I finished rebasing 6720b to trunk.* 🥳
I also done some light testing to be sure we haven't lost the lazy hydrati... - 08:29 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Ioana-Cristina Prioteasa wrote:
> [...]
> The testing plan is now complete. While harness tests are currently unava... - 04:42 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- The two additional tests passing are *not* a direct result of 9317a. The failures occur when the outer join optimizat...
- 03:33 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- ETF passed .
02/05/2025
- 10:38 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Tested 150 performance tests and the average time for a run stands for what I observed in #9317-31.
|_.Scenario|_.... - 09:25 AM Feature #7020 (WIP): always use "expanded" extent fields
- I started removing some denormalized / custom-extent references and seems to work well.
But, there is an issue I for... - 04:09 AM Feature #7020: always use "expanded" extent fields
- So, should I remove all references to @denormalized@ / @custom-extents@ and keep just the @normalized@ and @expanded@...
- 07:41 AM Feature #6720: lazy hydration
- Usages of @getData@ I have analysed:
* @Persister.insert@ Here it is not checked whether all the fields are hydrated... - 03:46 AM Feature #6720: lazy hydration
- Committed @6720b/14923@. I have addressed the issue exposed in #6720-71 by changing the corresponding bit from @liveP...
- 07:22 AM Bug #9590: Double LOAD for each record in FWD
- Dănuț Filimon wrote:
> [...] but I am still struggling with the final @results.previous()@ call which triggers the a... - 06:56 AM Bug #9590: Double LOAD for each record in FWD
- My new approach was to take into consideration @results.isAutoFetch()@ when firing the trigger in @RecordBuffer.setRe...
- 05:40 AM Bug #9318: Make record nursery visible on removeRecords
- ETF Conversion went well, ran two tests using the default @implicit = false@ and @deleteIndex = null@, found no regre...
02/04/2025
- 04:18 PM Feature #9544: implement missing SESSION handle attributes
- You might as well make the gap marking change and let's just get this closed out.
- 01:48 PM Feature #9544: implement missing SESSION handle attributes
- I did basic tests and these seem to +work as expected+. Yet, the gaps seem so suggest there is still work to do here:...
- 01:18 PM Feature #9542: finish ORIGIN-HANDLE ProDataSet attribute
- One more thing:
In Ref manual, the attribute is reported as:... - 01:09 PM Feature #9542: finish ORIGIN-HANDLE ProDataSet attribute
- Actually the support for this attribute is 90% implemented. What is missing is the 'reset'. It seems like the @rules/...
- 10:36 AM Feature #6720: lazy hydration
- I probably found a possible problem with the usage of @getData@ in @Record.setPropertyValues@. The problem is that he...
- 07:14 AM Feature #6720: lazy hydration
- As @BaseRecord.getData@ is only used in about 10 places, my current plan is to make some testcases to stress out as m...
- 07:11 AM Feature #6720: lazy hydration
- I actually just managed also with persistent tables:...
- 05:24 AM Feature #6720: lazy hydration
- Andrei, even though it is not that prominent for __temp database, I think it is still applied if I am not mistaken. I...
- 05:20 AM Feature #6720: lazy hydration
- My current focus for now is to check if the rollback functionality works when the lazy hydration is in place. Unfortu...
- 03:23 AM Feature #6720: lazy hydration
- > In this case, all the fields are hydrated at the beginning instead of only the camelCase field when it is accessed....
- 03:13 AM Feature #6720: lazy hydration
- While I was going over the changes and trying to understand them, I tried a simple example that should have used the ...
- 08:50 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Ioana-Cristina Prioteasa wrote:
> Testing plan for *9317a*:
> * *Lorian[ls]/Andrei[ai]/Ioana[icp]*: Chui regression... - 08:19 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- The time is the total execution time of all queries executed during the test.
- 07:17 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- What is the timing reflect? The total time for a specific query? What was the query analyzed? Or do you mean all SQL ...
- 05:56 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- I enabled SQL logging during a performance test with a threshold of 0, ensuring all queries were logged. The test was...
- 03:08 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Ioana-Cristina Prioteasa wrote:
> Testing plan for *9317a*:
> * *Andrei[ai]*: large customer Gui application regres... - 07:13 AM Bug #9590: Double LOAD for each record in FWD
- Dănuț Filimon wrote:
> This was added in trunk/12101 for #5136.
Correction, the actual code from #9590-17 was add... - 03:55 AM Bug #9590: Double LOAD for each record in FWD
- Alexandru Lungu wrote:
> > The problem is that !shouldUpdateAnyLock(lockType) will be false because the query compon... - 03:48 AM Bug #9590: Double LOAD for each record in FWD
- Alexandru Lungu wrote:
> Why is this solution working? @fetch(true, lockType, false);@ was going to call @super.fetc... - 03:41 AM Bug #9590: Double LOAD for each record in FWD
- Why is this solution working? @fetch(true, lockType, false);@ was going to call @super.fetch(available, lockType, err...
- 03:34 AM Bug #9590: Double LOAD for each record in FWD
- Alexandru Lungu wrote:
> > The problem is that !shouldUpdateAnyLock(lockType) will be false because the query compon... - 03:29 AM Bug #9590: Double LOAD for each record in FWD
- > The problem is that !shouldUpdateAnyLock(lockType) will be false because the query component will have a dynamic pr...
- 02:34 AM 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...
02/03/2025
- 04:34 PM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Does this mean "back to the drawing board", or is there a way around this?
Ugh, this is t... - 04:27 PM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> So, pretty much all the errors I encountered while testing 7020c with expand-extents=tru... - 12:50 PM Feature #7020: always use "expanded" extent fields
- Ovidiu noted this when I posted that my attempt to import into the database with normalized extents resulted in too m...
- 12:08 PM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Constantin Asofiei wrote:
> > The regression testing needs to do a diff between current/tru... - 11:54 AM Feature #7020: always use "expanded" extent fields
- Constantin Asofiei wrote:
> The regression testing needs to do a diff between current/trunk DDLs and the new DDLs. ... - 11:42 AM Feature #7020: always use "expanded" extent fields
- The regression testing needs to do a diff between current/trunk DDLs and the new DDLs. We need to know how/if someth...
- 11:19 AM Feature #7020: always use "expanded" extent fields
- Greg Shah wrote:
> No, that tool is not ready yet. Please test using a normal import.
Results noted in #8982-8 - 09:30 AM 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... - 09:25 AM Feature #7020: always use "expanded" extent fields
- No, that tool is not ready yet. Please test using a normal import.
- 09:18 AM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> Roger Borrello wrote:
> > *No errors* in the build with @9537a-15672@. I was indicating... - 09:06 AM 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... - 08:57 AM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> Roger Borrello wrote:
> > There are 2 builds of the customer application using @9537a-1... - 06:47 AM Feature #7020: always use "expanded" extent fields
- > Could you send me an email (sp) with the details ?
Details can be discussed in #9537. - 02:16 AM 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... - 11:57 PM Feature #7020: always use "expanded" extent fields
- There are 2 builds of the customer application using @9537a-15672@, one as we have always built, and one using @denor...
- 09:29 AM Bug #9590: Double LOAD for each record in FWD
- Alexandru, you mentioned in the meeting the @Results.isAutoFetch()@ method which is used here:...
- 07:21 AM Bug #9590: Double LOAD for each record in FWD
- Dănuț Filimon wrote:
> The CompoundQuery ends up triggering the FIND once in the @CompoundQuery.last(), Object[] ids... - 07:13 AM Bug #9590: Double LOAD for each record in FWD
- The CompoundQuery ends up triggering the FIND once in the @CompoundQuery.last(), Object[] ids = retrieve(LAST, lockTy...
- 06:37 AM Bug #9590: Double LOAD for each record in FWD
- I've managed to fix the AdaptiveQuery scenario, currently looking into fixing the CompoundQuery scenario.
- 03:06 AM Bug #9590: Double LOAD for each record in FWD
- There's an issue with #9590-9, especially with how triggers are executed for certain result sets. In the AdaptiveQuer...
- 05:06 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- *9317a is rebased*, the revisions that need testing: *15679 - 15689*.
- 04:56 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- In the trunk version, @collectPropertyMatches@ defaults them to false and -1 when creating the @AstWalkListener@, so ...
- 04:39 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Rebasing 9317 cause some issues because of *trunk rev. 15656*:...
- 02:56 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Testing plan for *9317a*:
* *Ioana[icp]*: large customer application unit tests and regression tests - DONE
* *Andr...
01/31/2025
- 10:03 AM 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... - 07:09 AM 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...
- 07:08 AM 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... - 04:25 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- h2. ..
Alexandru Lungu wrote:
> > So here the emitted sql differs and without the changes the where clause coming... - 04:20 AM Feature #6720: lazy hydration
- Andrei, please attempt to rebase *6720b* to latest trunk and continue the effort here. We can talk before picking up ...
- 03:56 AM Bug #9318: Make record nursery visible on removeRecords
- Alexandru Lungu wrote:
> Review of 9318a:
> * Please avoid overloading @removeRecords@ and enforce all callers to d... - 01:19 AM Bug #9318: Make record nursery visible on removeRecords
- Rebased *9318a* to latest *trunk/15676*, the branch is now at revision *15679*.
Currently working on addressing th...
01/30/2025
- 05:41 PM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Roger Borrello wrote:
> > Stefanel Pezamosca wrote:
> > > *Roger* (or someone who can), co... - 10:59 AM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Stefanel Pezamosca wrote:
> > *Roger* (or someone who can), could you help by testing *9537... - 10:13 AM 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... - 10:31 AM Bug #9595: Records accessed from dynamic buffers remain LOCKed until the user context is destroyed
- +Eric
- 10:27 AM Bug #9595: Records accessed from dynamic buffers remain LOCKed until the user context is destroyed
- I am facing some issues related to (un-)locking of records from (dynamic) buffers. Consider the following 2 procedure...
- 10:19 AM Bug #9595 (WIP): Records accessed from dynamic buffers remain LOCKed until the user context is de...
- 09:59 AM Bug #9317 (Internal Test): FIRST/LAST clauses can avoid generating sub-selects if the WHERE claus...
- > So here the emitted sql differs and without the changes the where clause coming from the OF clause is not included....
- 07:56 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- For the case @baseWhere == null@ the subselect is not to be generated. This was overlooked. And now it becomes clear ...
- 06:10 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- h2. --...
- 09:47 AM Bug #9318 (WIP): Make record nursery visible on removeRecords
- Review of 9318a:
* Please avoid overloading @removeRecords@ and enforce all callers to decide what kind of delete th... - 02:03 AM Bug #9318: Make record nursery visible on removeRecords
- Alexandru Lungu wrote:
> 9318a is at rev. 15618 (which doesn't include your latest changes).
Sorry about that, th... - 09:43 AM Bug #9590: Double LOAD for each record in FWD
- Using an AdaptiveQuery, the problem is this:...
- 09:14 AM Bug #9590: Double LOAD for each record in FWD
- Octavian Adrian Gavril wrote:
> Yes, the test case is complete. I got the result using *9509a/15650* which has some ... - 08:59 AM Bug #9590: Double LOAD for each record in FWD
- Yes, the test case is complete. I got the result using *9509a/15650* which has some changes for @CompoundQuery@. The ...
- 08:55 AM Bug #9590: Double LOAD for each record in FWD
- I followed up the first run of the test with another one and the @file.txt@ now contains:...
- 08:50 AM Bug #9590: Double LOAD for each record in FWD
- Tested with *trunk/15674*, the output of @file.txt@ was:...
- 08:34 AM Bug #9590 (WIP): Double LOAD for each record in FWD
01/29/2025
- 11:16 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Review of 9317a:
* @if (joinRef != null && !joinRef.equals(ref))@ this makes the query matching a bit more relaxed... - 11:02 AM Bug #9318: Make record nursery visible on removeRecords
- 9318a is at rev. 15618 (which doesn't include your latest changes).
- 09:22 AM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> *Roger* (or someone who can), could you help by testing *9537a* with @denorm_extents==tr... - 08:20 AM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> Hynek Cihlar wrote:
> > Code review 7020c. The UI changes look OK to me.
> >
> > Th... - 08:13 AM 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... - 08:02 AM Feature #7020: always use "expanded" extent fields
- Code review 7020c. The UI changes look OK to me.
There are some files that are missing file history entries. - 07:34 AM 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...
- 07:19 AM Feature #7020: always use "expanded" extent fields
- > *Greg/Roger*: I want to ask: Do you think we should bring the UI fixes for @denorm-extents=true@ in another branch ...
- 03:59 AM 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...
- 04:07 AM Bug #9590: Double LOAD for each record in FWD
- This testcase is generating the following output:...
- 04:03 AM Bug #9590 (WIP): Double LOAD for each record in FWD
01/28/2025
- 09:04 AM 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...
- 08:40 AM Feature #7020: always use "expanded" extent fields
- +Hynek to review the UI changes.
- 08:32 AM 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 @... - 05:30 AM 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 ... - 02:27 AM Feature #7020: always use "expanded" extent fields
- I have committed to 7020c revision 15669:
* Fixed inconsistency in frame widget handling when using denorm-extents.
... - 07:14 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- I build the following testcase:...
- 05:11 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- I think 4GL shows a compile error, right? In that case, FWD shouldn't be fixed as it presumes correct 4GL input.
Fo...
01/27/2025
- 09:20 AM Feature #7020: always use "expanded" extent fields
- I found a solution for the compilation issue:...
- 07:01 AM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> *Ovidiu*, I have the following testcases:
> [...] Converted to:
> [...] And the sql: ... - 04:14 AM Feature #7020: always use "expanded" extent fields
- *Ovidiu*, I have the following testcases:...
- 07:47 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Trying to create a test using the OF keyword, I stumbled upon another bug that might need fixing.
With the schema de... - 03:00 AM Bug #9318 (Review): Make record nursery visible on removeRecords
- Addressed the review from #9318-15 in *9318a/15589*. I removed @implicitBulkDelete@ and @deleteIndex@ members and cre...
01/24/2025
- 11:24 AM Support #4060: investigate converting extent fields to array columns
- I think this is dialect dependent. If all supported dialects had a fast native support for this, then the mapping wou...
- 07:26 AM Support #4060: investigate converting extent fields to array columns
- I believe our testing showed that array columns are faster than using "normalized" (secondary) array tables. We are ...
- 11:05 AM Feature #9577: persist the artifacts from dynamic query parsing/conversion (including the JAST) a...
- Indeed, this will have a great impact for queries executed early, during server startup. We can pre-train the server ...
- 07:39 AM Feature #9577: persist the artifacts from dynamic query parsing/conversion (including the JAST) a...
- Parsing dynamic queries is time consuming, which is why we cache them. As Ovidiu aptly notes in #9538-18, most of th...
- 07:29 AM Feature #9577 (New): persist the artifacts from dynamic query parsing/conversion (including the J...
- 07:45 AM Feature #6710: persist dynamic temp-tables across server restarts
- Didn't we implement this in #8233? Do we have full documentation for this? Is it linked into our documentation in a...
- 07:27 AM Support #4058: consider denormalizing tables as the default approach
- Can we do this with #7020?
01/23/2025
- 06:56 AM 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 ...
- 05:04 AM 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.
01/22/2025
- 04:13 AM Bug #9133: Array subscript is out of range stops the evaluation of other expressions in the where...
- Serban, can you test the scenario from #9189-1 with @9133b@ , please?
I expect to see some @SEVERE@ logs of this f... - 04:04 AM Bug #9133: Array subscript is out of range stops the evaluation of other expressions in the where...
- Rebased the branch to latest trunk and committed to @9133b / rev 15656@ :...
01/21/2025
- 05:08 PM Feature #7020 (WIP): always use "expanded" extent fields
- 10:01 AM Bug #9133 (Internal Test): Array subscript is out of range stops the evaluation of other expressi...
- I am OK with the changes in 9133b. Only thing is that the arguments should be aligned to @String.format@ first argume...
- 09:52 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- > Overall, I would want to refactor a bit the javadoc/parameter and method names to reflect the join with a FIRST/LAS...
- 09:01 AM Bug #9318 (WIP): Make record nursery visible on removeRecords
- I am OK with the "backbone" of 9318a.
* However, I am not enjoying the @implicitBulkDelete@ and @deleteIndex@ class...
01/20/2025
- 09:34 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- I went ahead and started testing the changes, on a big customer application I tested regression tests and the results...
- 05:45 AM Bug #9383 (Review): Cache only the current delegate on transaction commit if a ProgressiveResults...
- After working with a test case and having a look at the existent problems, I came to the conclusion that I should rev...
01/17/2025
- 04:16 PM Feature #9559: no-op implementations for obsolete record phrase and query options
- Likewise, the QUERY-TUNING option for queries must be ignored, since query planning is left to the RDBMS implementation.
- 04:07 PM Feature #9559: no-op implementations for obsolete record phrase and query options
- The TABLE-SCAN record phrase option will be a no-op, since the database's query planner will decide whether or not to...
- 04:06 PM Feature #9559 (New): no-op implementations for obsolete record phrase and query options
- 08:24 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Rebased *9383a* to latest *trunk/15651*, the branch is now at revision *15652*.
I managed to create examples after... - 05:46 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Committed on *9317a rev.15629* the changes needed based on the code review.
For the @PreselectQuery@ change, Alex is...
01/16/2025
- 04:37 PM Feature #9549: implement missing metadata features
- Some of these may be implemented to a greater degree than marked. If so, the gap marking needs to be fixed.
* @_fi... - 04:33 PM Feature #9549 (New): implement missing metadata features
- 04:16 PM Feature #9546: investigate and implement field options, if missing
- Options:
* LOB-AREA
* LOB-BYTES
* LOB-SIZE
* CLOB-CODEPAGE
* CLOB-COLLATION
* CLOB-TYPE - 04:15 PM Feature #9546 (New): investigate and implement field options, if missing
- 03:54 PM Feature #9545: confirm/add table parameter support
- @TABLE@ Parameters:
* @BY-REFERENCE@ (full/partial)
* @BY-VALUE@ (full/partial)
* @BIND@ (full/partial)
@KW_B... - 03:51 PM Feature #9545 (Review): confirm/add table parameter support
- 03:47 PM Feature #9544: implement missing SESSION handle attributes
- Attributes:
* @FIRST-BUFFER@
* @FIRST-QUERY@ - 03:46 PM Feature #9544 (Test): implement missing SESSION handle attributes
- 03:45 PM Feature #9543: implement missing BUFFER attributes
- Attributes:
* @AUTO-SYNCHRONIZE@ (none/none)
* @CAN-READ@ (none/none) - 03:44 PM Feature #9543 (Test): implement missing BUFFER attributes
- 03:42 PM Feature #9542: finish ORIGIN-HANDLE ProDataSet attribute
- Missing attributes:
* <table_handle>:ORIGIN-HANDLE (none/none) - 03:41 PM Feature #9542 (Test): finish ORIGIN-HANDLE ProDataSet attribute
01/15/2025
- 08:50 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Overall, I would want to refactor a bit the javadoc/parameter and method names to reflect the join with a FIRST/LAST ...
- 05:26 AM Bug #9317: FIRST/LAST clauses can avoid generating sub-selects if the WHERE clause matches a uniq...
- Alexandru Lungu wrote:
> I think this should be assessed now. Most of the PK/FK are groups of more than 1 field in #... - 07:46 AM Bug #9078: emit FindQuery as (reused) variables
- Fixed the problem from #9078-75 in *9078b/15625*. The rules rely on the "extbufid" annotation to emit the @setMultiTe...
- 06:28 AM Bug #9078: emit FindQuery as (reused) variables
- While working on a few tests, I found another conversion regression when using multi-tenancy where a find query that ...
- 03:12 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078b/15624*. Fixed conversion compatibility with multi-tenancy, ETF conversion passed (matches previous c...
Also available in: Atom