Activity
From 02/28/2026 to 03/29/2026
03/27/2026
- 10:26 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Please tell when to port these changes to custom customer build line.
- 10:24 AM Bug #9383 (Test): Cache only the current delegate on transaction commit if a ProgressiveResults i...
- Branch 9383c was merged into trunk as rev. 16488 and archived.
- 10:15 AM Bug #9383 (Merge Pending): Cache only the current delegate on transaction commit if a Progressive...
- > Yes, I have made the customer application setup just for that.
Nice job! Please proceed with merging 9383a to tr... - 10:14 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Yes, I have made the customer application setup just for that.
- 10:13 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Do you also mean #10275?
- 10:11 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have already tested that and this is why I have moved from @OFFSET@ approach to fetch by pk.
Every change that I h... - 10:10 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > All testing was done and it can be scheduled for merging.
#11154 is the number one priority for testing this. We... - 10:08 AM Bug #7841 (Test): Invalid conversion of temp table DMO when using clob/blob fields
- Branch 7841a was merged into trunk as rev. 16487 and archived.
- 10:00 AM Bug #7841 (Merge Pending): Invalid conversion of temp table DMO when using clob/blob fields
- Please merge this to trunk now.
- 03:35 AM Bug #7841: Invalid conversion of temp table DMO when using clob/blob fields
- I forgot about this, the regression testing has passed for 7841a.
I think we can merge this. - 09:44 AM Bug #11332: SimpleResults.rows might store Object instead of Object[]
- There is a bug in @SimpleResults.rows@ so that the generic is bypassed forcefully somewhere so that a plain Object is...
- 09:42 AM Bug #11332 (New): SimpleResults.rows might store Object instead of Object[]
- 05:58 AM Feature #11291 (Review): Improve h2 locking system
- I changed the meta db to use mvstore and fixed the unique constraint violation in @databaseConnected@ by using @merge...
- 04:19 AM Feature #11291: Improve h2 locking system
- The problem is the pattern used in @databaseConnected@, currently id does @select@ -> @insert@/@update@ and assumes (...
03/26/2026
- 11:41 AM Feature #11291: Improve h2 locking system
- For testing I am using a script that starts a number of concurrent batch clients that connect to the database.
With ...
03/25/2026
- 11:16 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Ok, thanks!
All testing was done and it can be scheduled for merging. - 11:16 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Tests passed successfully, nothing unusual.
- 09:21 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- No problem.
I would have been tested by myself, but I am struggling with the disk space. - 09:18 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Teodor Gorghe wrote:
> *Stefanel*, when you have time, please test this branch on your main application (I have aske... - 09:12 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16429* on task branch *9383c*:
- Fixed regressions from ChUI regression tests.
Now, the ChUI ... - 09:36 AM Feature #10491: Tool to standardize PG cluster creation
- Ovidiu Maxiniuc wrote:
> Roger Borrello wrote:
> > Ovidiu, I have been seeing the below after the server connects t... - 07:57 AM Feature #10491: Tool to standardize PG cluster creation
- Roger Borrello wrote:
> Ovidiu, I have been seeing the below after the server connects to the DB. Do you know where ...
03/23/2026
- 11:29 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have found the issue.
I have didn't looked that much when the query is @PreselectQuery@ from conversion.
The issu... - 04:44 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- About the regression from ChUI Regression tests, I have debugged the test, but unfortunate, I was unable to see the i...
- 08:30 AM Feature #9305: Replace begins with interval based conditional
- I have also tested the difference between @LIKE@ and @RANGE CHECK@ on @PSQL@.
When the @libc@ collation provider i... - 07:55 AM Feature #9305: Replace begins with interval based conditional
- I have also noticed that for Western characters, there is no difference between @BASIC@ and @ICU-UCA@ on @RANGE CHECK...
- 07:50 AM Feature #9305: Replace begins with interval based conditional
- This is another example of @RANGE CHECK@ vs @BEGINS@, using @UTF-8@ collation on 4GL:...
03/20/2026
- 04:49 PM Bug #9383 (Internal Test): Cache only the current delegate on transaction commit if a Progressive...
- Teodor Gorghe wrote:
> Committed revision *16428* on task branch *9383c*:
Good job! Please go ahead with regressi... - 08:07 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- On ChUI regression tests, there is one unexpected test which fails now. I am investigating this once the ChUI regress...
- 07:02 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16428* on task branch *9383c*:
- Fixed SQLServer issue (set the limit to be 0). - 06:52 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have found where the @LIMIT@ is inserted, and that is because the @maxLimit@ is set. I will set it to 0 since is no...
- 06:38 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- There is actually a regression from *9383c* on *SQLServer*.
The issue comes from the fact that you can't use @OFFSET... - 04:20 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16427* on task branch *9383c*:
- Changes to address #9383-129 observation (no functional differe... - 01:40 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur Școlnic wrote:
> With c3p0, this worked by accident because @connection.close()@ doesn't actually close the co... - 12:03 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Ovidiu Maxiniuc wrote:
> I agree.
> The drop of c3p0 pooling support for in-memory databases was just an optimisati... - 07:07 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Done:
> Port of trunk/16478: Reverted changes done by 11288a in trunk/16471. (refs: #11288) - 06:56 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Alexandru Lungu wrote:
> Branch 11288c was merged into trunk as rev. 16478 and archived.
Please also patch 10614_ma... - 06:55 AM Bug #11288 (WIP): Check if c3p0 is required for in-memory databases
- Branch 11288c was merged into trunk as rev. 16478 and archived.
- 06:53 AM Bug #11288 (Merge Pending): Check if c3p0 is required for in-memory databases
- 11288c now has the revert of trunk/16471.
I am preparing to merge it to trunk. - 06:44 AM Bug #11288: Check if c3p0 is required for in-memory databases
- > Alex: can you take care of the rollback?
Now is WIP. - 06:03 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Alex: can you take care of the rollback?
- 09:35 PM Bug #11288: Check if c3p0 is required for in-memory databases
- I agree.
The drop of c3p0 pooling support for in-memory databases was just an optimisation, as proven by the initial... - 09:32 AM Feature #10491: Tool to standardize PG cluster creation
- Updated in revision 16473 when I realized the external tool @create_roles.sql@ was not included. This version creates...
- 09:17 AM Feature #9305: Replace begins with interval based conditional
- This is one difference between @BEGINS@ and @range check@, on @BASIC@ collation:...
03/19/2026
- 02:15 PM Bug #11288 (WIP): Check if c3p0 is required for in-memory databases
- Alex/Ovidiu: we need to back out 11288a changes from trunk and 10614_main, via a branch 11288c:
* we are now bypassi... - 01:41 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Please check if we are not re-using a prepared statement after the connection has closed. Also, post a small test, ...
- 01:39 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Constantin Asofiei wrote:
> I don't understand this - are you saying there is some async processing in the backgroun... - 01:33 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur Școlnic wrote:
> With direct connections, @close()@ is immediate. So the sequence was effectively:
> 1. setBl... - 01:23 PM Bug #11288 (Review): Check if c3p0 is required for in-memory databases
- We were using @stmt.setBlob@ in @TypeManager@, which in H2 doesn't immediately send the data to the database. Instead...
- 08:21 AM Bug #11288 (Internal Test): Check if c3p0 is required for in-memory databases
- Let me know when you find the issue.
- 08:19 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Constantin,
There is an issue with an unit test from the large gui application suite, I need to see what is is first... - 07:47 AM Bug #11288 (Merge Pending): Check if c3p0 is required for in-memory databases
- Artur, add history entry and merge to trunk and 10614_main now.
03/18/2026
- 05:01 PM Feature #10491: Tool to standardize PG cluster creation
- Ovidiu Maxiniuc wrote:
> [...]
> ...but my guess is that it happens at the time the secondary databases (dirty/meta... - 08:56 AM Feature #10491: Tool to standardize PG cluster creation
- Ovidiu Maxiniuc wrote:
> Roger,
> I remember seeing that warning. I did not investigate what is the exact cause, bu... - 12:44 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Ovidiu, I also added cfg initialization.
- 12:27 PM Bug #11288 (Review): Check if c3p0 is required for in-memory databases
- Ovidiu, I don't think there is other initialization missed, the rest was c3p0 specific.
Please review 11288b.
I alr... - 12:01 PM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur: Please update [[regression:Open Regressions in FWD v4]] with the details.
- 11:59 AM Bug #11288 (WIP): Check if c3p0 is required for in-memory databases
- Thank you, Stefanel.
Ovidiu, I'll add this and see if I forgot something else in the 'b' branch. - 11:39 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Artur, trunk/16471 seems to have a regression. The new @ConnectionProvider.getH2Connection@ is missing this piece of ...
- 08:13 AM Bug #11288 (Test): Check if c3p0 is required for in-memory databases
- I did port the change.
- 06:01 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Since this task was derived from #11282, I assume the patch should be delivered to the custom branch also?
- 06:00 AM Bug #11288: Check if c3p0 is required for in-memory databases
- 11288a was merged to trunk/16471.
- 05:47 AM Bug #11288 (Merge Pending): Check if c3p0 is required for in-memory databases
- Please merge 11288a to trunk after 11068c.
- 03:56 AM Bug #11288: Check if c3p0 is required for in-memory databases
- I think we can merge this one.
- 10:31 AM Bug #10385 (Test): Incorrect reset of the cursor cache in Reposition
- 10:28 AM Bug #10385 (Internal Test): Incorrect reset of the cursor cache in Reposition
- This task is the same issue as 11021, so it can be closed.
- 06:21 AM Feature #9545: confirm/add table parameter support
- Committed on *9545a, rev. 16473*.
- improved shouldRaiseBeforeError method logic, to handle FWD actor and paramete...
03/17/2026
- 06:59 PM Feature #10491: Tool to standardize PG cluster creation
- Roger,
I remember seeing that warning. I did not investigate what is the exact cause, but my guess is that it happen... - 04:14 PM Feature #10491: Tool to standardize PG cluster creation
- Ovidiu: Please review.
Roger: This should be in the FWD project under @tools/scripts/@. - 10:50 AM Bug #11288: Check if c3p0 is required for in-memory databases
- I tested the multi tenant application since it's the most complex in terms of the db infrastructure. I spotted no reg...
- 10:40 AM Feature #9545: confirm/add table parameter support
- Committed on *9545a, rev. 16473.*
Fixed different error handling logic.
03/16/2026
- 11:14 AM Bug #11288 (Internal Test): Check if c3p0 is required for in-memory databases
- All my observations seems to be addressed. Please start the regression tests.
- 06:56 AM Bug #11288: Check if c3p0 is required for in-memory databases
- Ovidiu Maxiniuc wrote:
> +Review of 11288a / r16469+
> ** line 256: the defaulting to @TenantManager.DEFAULT_TENANT... - 09:19 AM Feature #11291: Improve h2 locking system
- Setting a certain lock mode for certain h2 databases is a reasonable solution, anything that involves changing the ov...
- 09:00 AM Feature #11291: Improve h2 locking system
- > Switch to MVStore, which handles concurrency more robustly and avoids these locking complications.
If this is pr... - 08:47 AM Feature #11291: Improve h2 locking system
- After extensive analysis and trial and error, modifying the H2 @PageStore@ locking system is proving extremely comple...
- 08:14 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
In @BatchResults.java@:
* there is a missing @*@ at line 36;
* lines 519/520 and 583/584: by moving the concatena...- 02:37 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Addressed the code review #9383-127 in +9383c / r16426+.
- 05:38 AM Feature #9545: confirm/add table parameter support
- Changes in current form passed initial conversion and regression tests on ETF.
- 05:36 AM Feature #9545 (Review): confirm/add table parameter support
- Committed on *9545a, rev. 16470*.
- Before table of the REFERECE-ONLY temp-table is passed as parameter to RecordB...
03/14/2026
- 09:39 PM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- +Review of 9383c / r16422..16425+
I focused only to latest changes. Let me know if I should review the full change... - 08:17 PM Bug #11288: Check if c3p0 is required for in-memory databases
- +Review of 11288a / r16469+
I think the code is good. Except for restricting the direct connection only to in-memo...
03/13/2026
- 09:11 AM Feature #11291: Improve h2 locking system
- Important note:
H2 has a general invariant - *the lock must be on the @database@ instance*, this is expected through... - 08:54 AM Bug #10772: NUM-RESULTS on a FOR EACH query fails
- All testing was done and the branch is ready to be merged to trunk.
- 07:33 AM Bug #11288 (Review): Check if c3p0 is required for in-memory databases
- Ovidiu, please review 11288a.
- 07:32 AM Bug #11288 (WIP): Check if c3p0 is required for in-memory databases
- 11288a contains several changes:
* refactored @JdbcDataSource@ to manage only persistent db connections
* small re... - 03:24 AM Bug #11288: Check if c3p0 is required for in-memory databases
- For single threaded performance comparison of h2 direct connection and pooling, please see #11282-40.
With a more 'r... - 05:26 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- *Ovidiu*, please take a look into the changes. Please tell if this is alright.
- 05:22 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *1832* on *xfer testcases*:
- Added tests for BatchResults (#9383).
Committed revision *16423*... - 02:48 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Status from yesterday:
- I have tested different queries, outer-join, with 2 or more components, query with only one...
03/12/2026
- 08:04 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Committed revision *16422* in task branch *9383c*:
- When possible, fetch the records in batch by PK.
I will do s... - 06:17 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Awesome!!!
- 05:59 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have tested #11154 and now it takes 2 minutes (from 4 minutes).
- 05:24 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have great news.
I have tested #9383 with PK fetching in batches, and I see very noticible changes in performance.... - 04:42 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I think the easiest solution for this is to fetch the records in batches, by PK (eg. @IN@ syntax from SQL). This will...
- 07:58 AM Feature #11291 (WIP): Improve h2 locking system
- 06:37 AM Feature #11291: Improve h2 locking system
- In H2 using the PageStore engine, writes acquire locks on database pages or tables. In a highly concurrent environmen...
- 06:34 AM Feature #11291 (Review): Improve h2 locking system
03/11/2026
- 09:29 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I can confirm that #11154 is caused by fetching smaller batches instead of one with bigger batch size.
Suppose you... - 08:31 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- There is no dynamic mode, which I have thought.
The issue from #11154 comes from the fact that the @Session@ cache i... - 08:00 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I have managed to get the #11154 up and running, but I see that there is a regression also with 9383c (baseline time ...
- 08:13 AM Bug #11288: Check if c3p0 is required for in-memory databases
- This task is to investigate the performance benefit of c3p0 for in-memory databases.
* _temp doesn't use c3p0 and it... - 08:11 AM Bug #11288 (Test): Check if c3p0 is required for in-memory databases
- 08:07 AM Bug #10776 (Pending): FFC.touch standing out in profiling
- This effort was integrated in #11037
- 07:29 AM Feature #11287: Leverege the pg_prewarm function to improve cold server performance
- An extension of this task is fine tuning the shared buffer cache size, the default is quite modest at 128Mb, I think ...
- 07:25 AM Feature #11287: Leverege the pg_prewarm function to improve cold server performance
- @pg_prewarm@ is a PostgreSQL extension that loads tables or indexes into memory (the shared buffer cache) before they...
- 07:09 AM Feature #11287 (New): Leverege the pg_prewarm function to improve cold server performance
03/10/2026
- 02:08 PM Feature #9545: confirm/add table parameter support
- h3. Buffer / Temp-Table explicit deletion...
03/09/2026
- 08:56 AM Feature #10491: Tool to standardize PG cluster creation
- Ovidiu, I have been seeing the below after the server connects to the DB. Do you know where this function comes from?...
- 08:45 AM Bug #11161 (Review): fail gracefully when the database connection can not be established
- I committed the initial version of the fix. With the new approach, if the database connection pool is exhausted, C3P0...
- 07:40 AM Feature #9545: confirm/add table parameter support
- *MyClass1.cls*...
03/05/2026
- 10:06 AM Bug #11279: RecordNursery invalidated for a rollabacked transient record
- > Now I do a undo, return with a temp-table that is NO-UNDO, this means that the record is still retained in the buff...
- 09:52 AM Bug #11279: RecordNursery invalidated for a rollabacked transient record
- *start.p*...
- 09:38 AM Bug #11279 (New): RecordNursery invalidated for a rollabacked transient record
03/04/2026
- 12:56 PM Bug #11231 (Test): FastFindCache clear operations may leak memory
- 09:57 AM Bug #11231: FastFindCache clear operations may leak memory
- 11231a was merged to trunk/16455.
- 09:40 AM Bug #11231 (Merge Pending): FastFindCache clear operations may leak memory
- I tested POC, everything is fine. Please proceed with merging.
- 03:42 AM Bug #11231: FastFindCache clear operations may leak memory
- I also tested harness, webui navigation and reports, everything looks ok, can we merge?
- 03:41 AM Bug #11231: FastFindCache clear operations may leak memory
- I ran the unit tests and a few smoke test scenarios for another large GUI application, and I didn’t see any obvious i...
- 03:40 AM Bug #11231: FastFindCache clear operations may leak memory
- Unit tests of a large customer application passed.
- 11:15 AM Feature #4369: implement stateless FWD server clustering
- Yes
- 11:10 AM Feature #4369: implement stateless FWD server clustering
- Greg Shah wrote:
> Let's discuss this in another task (create one for this). I don't want to pollute this one with ... - 10:25 AM Feature #4369: implement stateless FWD server clustering
- Let's discuss this in another task (create one for this). I don't want to pollute this one with devops/scripting dis...
- 09:44 AM Feature #4369: implement stateless FWD server clustering
- Alexandru Lungu wrote:
> FYI: I created https://proj.goldencode.com/projects/p2j/wiki/Stateless_Server_Clustering fo... - 09:33 AM Feature #4369: implement stateless FWD server clustering
- For the configuration, the @./deploy/server/prepare_dir.sh@ can be updated to look for a new section in the JSON, whi...
03/03/2026
- 02:19 PM Bug #11235 (Test): Deprovisioning tenants does not clear data sources
- 02:18 PM Bug #11235: Deprovisioning tenants does not clear data sources
- 11235a was merged to trunk as revision 16453.
- 03:04 AM Feature #9545: confirm/add table parameter support
- I have been investigated the error handling cases of passing parameters between *calling* and *called* procedure, whe...
03/02/2026
- 11:46 AM Bug #7841 (Internal Test): Invalid conversion of temp table DMO when using clob/blob fields
- Thanks, can be queued for testing.
- 08:44 AM Bug #7841 (Review): Invalid conversion of temp table DMO when using clob/blob fields
- Added other missing field_clob, field_blob and field_com_handle in accumulate.rules, frame_generator.xml, common-prog...
- 03:41 AM Bug #7841 (WIP): Invalid conversion of temp table DMO when using clob/blob fields
- Sure, I’ll check.
- 03:38 AM Bug #7841: Invalid conversion of temp table DMO when using clob/blob fields
- Stefanel, please add also @field_com_handle@ there - this is the only one which is still missing.
Also, do a searc... - 02:35 AM Bug #7841 (Review): Invalid conversion of temp table DMO when using clob/blob fields
- Created branch 7841a from trunk/16448.
Committed fix in 7841a revision 16449. - 08:58 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Do we need to port the changes to @custom_build_line@?
- 08:12 AM Bug #11235 (Merge Pending): Deprovisioning tenants does not clear data sources
- Please merge after 11224a
- 08:33 AM Bug #11231 (Internal Test): FastFindCache clear operations may leak memory
- I am OK with the changes, please proceed with testing.
- 05:47 AM Bug #11231: FastFindCache clear operations may leak memory
- Alexandru, I addressed the issues, please review 11231a/16436.
Also available in: Atom