Activity
From 02/17/2026 to 03/18/2026
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.
02/27/2026
- 05:34 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Ok, thanks!
- 05:33 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Some of the problems i saw were because i was using an older conversion. I've fixed my setup and will retest.
- 05:30 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian, do you have any status update?
- 04:23 AM Bug #7999: FWD does not honor FIELDS/EXCEPT at dynamic queries
- Rebased *7999a* to trunk *rev. 16447*.
This branch will work for the large majority of case.
There is only a sm... - 02:49 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu Maxiniuc wrote:
> Well, that's a philosophical question :).
> When a tenant is deleted, beside the effect on... - 02:42 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Smoke-testing a customer app with 11235a passed.
02/26/2026
- 05:39 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Well, that's a philosophical question :).
When a tenant is deleted, beside the effect on the database we discussed a... - 01:46 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu, I meant on tenant delete, do we need to disconnect the private database?
- 12:28 PM Bug #11235: Deprovisioning tenants does not clear data sources
- This method is the implementation of @DISCONNECT@ statement. Unfortunately, this is not documented in javadoc. Theref...
- 05:29 AM Bug #11235: Deprovisioning tenants does not clear data sources
- @ConnectionManager.disconnect@ expects the logical db name, which can/should be the same for all the tenant databases...
- 04:55 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu Maxiniuc wrote:
> +Review of 11235a / r16440+
>
> Nicely done! I think the code will work as expected.
... - 10:22 AM Bug #7841 (WIP): Invalid conversion of temp table DMO when using clob/blob fields
- I took a quick look here and found this in @rules/include/common-progress.rules@ -> @<function name="create_temp_tabl...
- 09:57 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Eduard, the root cause is that the dynamic temp-table created for an argument does not i... - 08:28 AM Feature #9545: confirm/add table parameter support
- Eduard, the root cause is that the dynamic temp-table created for an argument does not inherit the undoable from the ...
- 04:47 AM Feature #9545: confirm/add table parameter support
- We can divide this in 2 cases temp-table *with* @no-undo@ and *without* @no-undo@ option....
- 02:52 AM Feature #9545: confirm/add table parameter support
- Eduard, so please check why FWD doesn't clear the record from the buffer,or otherwise doesn't mark it as 'deleted'. ...
- 02:33 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> After @doBlock1@ I would expect that in 4GL the buffer has no record (as the tx was roll... - 09:54 AM Bug #11231: FastFindCache clear operations may leak memory
- Review of 11231a:
* @implements Map<K, V>@ clause should be on a new line
* @MINIMAL_LOAD_FACTOR@ should be @minima...
02/25/2026
- 03:34 PM Bug #11235 (Internal Test): Deprovisioning tenants does not clear data sources
- +Review of 11235a / r16440+
Nicely done! I think the code will work as expected.
Please start the regression tests. - 11:29 AM Feature #9545: confirm/add table parameter support
- After @doBlock1@ I would expect that in 4GL the buffer has no record (as the tx was rolledback). Please check this.
- 11:25 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Is the buffer @httTest:default-buffer@ still holding the record when @OutputTableHandleC... - 10:53 AM Feature #9545: confirm/add table parameter support
- Is the buffer @httTest:default-buffer@ still holding the record when @OutputTableHandleCopier@ is copied?
- 10:51 AM Feature #9545: confirm/add table parameter support
- Constantin Asofiei wrote:
> Eduard Soltan wrote:
> > I think we need to make this method @finalizable@ aware that a... - 10:50 AM Feature #9545: confirm/add table parameter support
- Eduard Soltan wrote:
> I think we need to make this method @finalizable@ aware that a *rollback happened previously*... - 10:43 AM Feature #9545: confirm/add table parameter support
- start.p...
- 10:05 AM Bug #11161: fail gracefully when the database connection can not be established
- Greg Shah wrote:
> The @CONNECT@ must be in a *separate* @.p@. Call the @<connect_program>.p@ from *within* the 4GL... - 10:01 AM Bug #11161: fail gracefully when the database connection can not be established
- The @CONNECT@ must be in a *separate* @.p@. Call the @<connect_program>.p@ from *within* the 4GL code block that tri...
- 09:51 AM Bug #11161: fail gracefully when the database connection can not be established
- Do nested blocks like this:...
- 09:04 AM Bug #11161: fail gracefully when the database connection can not be established
- Maybe my tests are wrong, I can't seem to register the STOP
connect.p... - 08:50 AM Bug #11161: fail gracefully when the database connection can not be established
- In our past testing, the @STOP@ condition in disconnect cases can be caught, but only by a block that is outside of a...
- 08:40 AM Bug #11161: fail gracefully when the database connection can not be established
- When it comes to database shutdown during an open session:
1. program executed on the server - is terminated, error ... - 08:05 AM Bug #11161: fail gracefully when the database connection can not be established
- Artur Școlnic wrote:
> In OE, failure happens early.
> At the beginning of an unbound session:
> * A database conn... - 06:37 AM Bug #11161: fail gracefully when the database connection can not be established
- I was talking strictly about insufficient database connections, if the connection is interrupted during a session, I ...
- 06:33 AM Bug #11161: fail gracefully when the database connection can not be established
- > In OE, failure happens early.
What about a communications/network failure that happens later? - 04:24 AM Bug #11161: fail gracefully when the database connection can not be established
- *With the current infrastructure, handling database connection starvation remains challenging*
Key Challenges:
...
02/24/2026
- 12:17 PM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- I added cleanup for the dirty database sources and extended the source clearing to include the tenant update scenario...
- 09:48 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Understood, thank you.
> I got another question, using the tenant api, we can update a tenan... - 09:39 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Understood, thank you.
> I got another question, using the tenant api, we can update a tenan... - 09:35 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Understood, thank you.
I got another question, using the tenant api, we can update a tenant, including the urls. On ... - 09:17 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ovidiu, please comment on #11235-19.
As documented in javadoc of that method, the returned d... - 09:05 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Constantin Asofiei wrote:
> Do we have a dirty database instance in H2 for each tenant?
Yes. This is the architectu... - 08:57 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu, please comment on #11235-19.
- 08:51 AM Bug #11235: Deprovisioning tenants does not clear data sources
- The @sources@ map should contain for a tenant-enabled database:
* @N + 1@ sources for each (postgresql) permanent da... - 08:10 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> I would expect so. I am using just one tenant, so there are 2 dirty db, the default tenant an... - 08:10 AM Bug #11235: Deprovisioning tenants does not clear data sources
- I would expect so. I am using just one tenant, so there are 2 dirty db, the default tenant and the explicit one.
- 08:08 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ok, it makes sense, so we do need to clear only the data source for the dirty databases.
Do ... - 08:06 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ok, it makes sense, so we do need to clear only the data source for the dirty databases.
On tenant delete, this is n... - 07:52 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Also, what about the _temp database, where the temp tables reside? Shouldn't it also be tenan... - 07:52 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Ovidiu,
> I have a few questions:
> 1. Not all h2 databases are marked as @temp@, is this ... - 07:46 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Also, what about the _temp database, where the temp tables reside? Shouldn't it also be tenant specific and cleared o...
- 06:21 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu,
I have a few questions:
1. Not all h2 databases are marked as @temp@, is this expected?
2. The dirty data... - 02:33 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
02/23/2026
- 05:43 PM Bug #11235: Deprovisioning tenants does not clear data sources
- I realized that the datasource for dirty database (in-memory, h2 dialect) should also be processed (removed from @sou...
- 09:40 AM Bug #11235 (Internal Test): Deprovisioning tenants does not clear data sources
- +Review of 11235a/r16438+
Good job!
Please start the regression tests. Make sure there are no regressions with th... - 08:18 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Ovidiu,
Constantin raised the question of data source resources retention, mainly the helper threads, just to be on... - 04:06 AM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- It looks like I was wrong, the values are not overwritten, just a different context local instance of the connection ...
- 03:32 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
- Ovidiu,
I encountered an issues while working with @tenantsByDatabase@, adding a tenant with the same logical datab... - 02:18 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Not sure if it is relevant in these cases, but in certain broker modes, the contexts can be reused across appserver s...
02/20/2026
- 05:57 PM Bug #11235: Deprovisioning tenants does not clear data sources
- +Review of 11235a/r16436+
My bet is the changes will work as expected. Related to this revision I have only some l... - 09:29 AM Bug #11235 (Review): Deprovisioning tenants does not clear data sources
- I added the data source removal on tenant db removal.
Ovidiu, please review 11235a.
Collections affected by ten... - 04:58 AM Bug #11235 (WIP): Deprovisioning tenants does not clear data sources
- 05:43 AM Bug #11231: FastFindCache clear operations may leak memory
- Alexandru, I added a new implementation for the Map that shrinks if the load factor is low enough and used it for ff ...
02/19/2026
- 05:54 PM Bug #11235: Deprovisioning tenants does not clear data sources
- Indeed, at the moment when support for tenants was implemented, the operation of removing them did not take this aspe...
- 09:00 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Artur Școlnic wrote:
> Just to be sure, deprovisioning a tenant means simply deleting it via tenant API?
In FWD ter... - 08:58 AM Bug #11235: Deprovisioning tenants does not clear data sources
- Just to be sure, deprovisioning a tenant means simply deleting it via tenant API?
- 08:27 AM Bug #11235: Deprovisioning tenants does not clear data sources
- FWD creates a data source (connection pool) for each tenant, if one is deprovisioned, the data source is not cleared,...
- 08:25 AM Bug #11235 (Test): Deprovisioning tenants does not clear data sources
- 10:37 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:06 AM Feature #4369: implement stateless FWD server clustering
- FYI: I created https://proj.goldencode.com/projects/p2j/wiki/Stateless_Server_Clustering for documentation on this fe...
- 08:34 AM Bug #11236 (New): Buffers whose scope is restricted to an iterative block shoud be released durin...
- 08:09 AM Bug #11231: FastFindCache clear operations may leak memory
- Please note this change which moved from 'new instance' to 'clear':...
- 07:41 AM Bug #11231: FastFindCache clear operations may leak memory
- Alexandru Lungu wrote:
> I am concerned that the size represents the number of active elements, not the actual cap... - 07:38 AM Bug #11231: FastFindCache clear operations may leak memory
- > When clearing an L3 map, check its current size against a defined threshold:
I am concerned that the size repres... - 07:01 AM Bug #11231 (Review): FastFindCache clear operations may leak memory
- I used the following heuristics to alleviate the issue:
* On L3 clear –
When clearing an L3 map, check its current ... - 05:14 AM Bug #11231 (WIP): FastFindCache clear operations may leak memory
- 05:01 AM Bug #11231: FastFindCache clear operations may leak memory
- After refactoring FFCache to be driven by the @ReverseLookup@, so that there is only one unified LRU cache that contr...
- 04:43 AM Bug #11231 (Test): FastFindCache clear operations may leak memory
- 01:49 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- ChUI regression testing has passed.
02/18/2026
- 11:44 AM Feature #9545: confirm/add table parameter support
- I can confirm, I have personally tested it.
And I must apologise again. In my note #9545-18 I have actually looked... - 08:33 AM Feature #9545: confirm/add table parameter support
- Greg Shah wrote:
> Have these programs been tested on OE? Sometimes the OE documentation is incorrect, misleading o... - 08:24 AM Feature #9545: confirm/add table parameter support
- Have these programs been tested on OE? Sometimes the OE documentation is incorrect, misleading or incomplete.
- 06:18 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> Yet, I think the error is correct. Only the @test22.p@ is persistent. @test21.p@ is not. Th... - 06:10 AM Feature #9545: confirm/add table parameter support
- OK, sorry I was mislead by the persistent initialisation of @test22.p@.
Yet, I think the error is correct. Only th... - 05:42 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> The problem in #9545-12 testcase is that @start.p@ declares the temp-table @ttTest@ as @r... - 05:32 AM Feature #9545: confirm/add table parameter support
- Eduard Soltan wrote:
> I understand this, and already handled majority of this error cases in 9545a. What I am tryin... - 03:11 AM Feature #9545: confirm/add table parameter support
- Ovidiu Maxiniuc wrote:
> Eduard,
>
> You can only @BIND@ a temp-table to a @REFERENCE-ONLY@ temp-table. There are...
02/17/2026
- 06:16 PM Feature #9545: confirm/add table parameter support
- Eduard,
You can only @BIND@ a temp-table to a @REFERENCE-ONLY@ temp-table. There are two cases here (these are my ... - 08:48 AM Feature #9545: confirm/add table parameter support
- I could not find this anywhere in the documentation. My best guess is that for calling procedures that passes an actu...
- 07:08 AM Feature #9545: confirm/add table parameter support
- However in a slightly more complicated case, extracted from the testcases:
start.p... - 06:54 AM Feature #9545: confirm/add table parameter support
- start.p...
- 09:35 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Lorian Sandu wrote:
> I've started the @...@ script a few times and unfortunately it gets stuck (or works very slow)... - 09:30 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I've started the @conv-launch@ script a few times and unfortunately it gets stuck (or works very slow) at a step that...
- 01:43 AM Bug #10390: FIND FIRST buffer field change does not propagate into the next FIRST FIRST statements.
- About the testcases cross-session tests, they have passed.
I have run the ChUI regression testing and I see two un...
Also available in: Atom