Activity

From 02/25/2026 to 03/26/2026

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 ... Artur Școlnic

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. Teodor Gorghe
11:16 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used: Tests passed successfully, nothing unusual. Stefanel Pezamosca
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. Teodor Gorghe
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... Stefanel Pezamosca
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 ... Teodor Gorghe
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... Roger Borrello
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 ... Ovidiu Maxiniuc

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... Teodor Gorghe
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... Teodor Gorghe
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... Teodor Gorghe
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... Teodor Gorghe
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:... Teodor Gorghe

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... Ovidiu Maxiniuc
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... Teodor Gorghe
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). Teodor Gorghe
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... Teodor Gorghe
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... Teodor Gorghe
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... Teodor Gorghe
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... Ovidiu Maxiniuc
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... Eric Faulhaber
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) Alexandru Lungu
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... Constantin Asofiei
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. Alexandru Lungu
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. Alexandru Lungu
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. Alexandru Lungu
06:03 AM Bug #11288: Check if c3p0 is required for in-memory databases: Alex: can you take care of the rollback? Constantin Asofiei
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... Ovidiu Maxiniuc
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... Roger Borrello
09:17 AM Feature #9305: Replace begins with interval based conditional: This is one difference between @BEGINS@ and @range check@, on @BASIC@ collation:... Teodor Gorghe

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... Constantin Asofiei
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, ... Constantin Asofiei
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... Artur Școlnic
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... Constantin Asofiei
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... Artur Școlnic
08:21 AM Bug #11288 (Internal Test): Check if c3p0 is required for in-memory databases: Let me know when you find the issue. Constantin Asofiei
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... Artur Școlnic
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. Constantin Asofiei

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... Eric Faulhaber
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... Roger Borrello
12:44 PM Bug #11288: Check if c3p0 is required for in-memory databases: Ovidiu, I also added cfg initialization. Artur Școlnic
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... Artur Școlnic
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. Greg Shah
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. Artur Școlnic
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 ... Stefanel Pezamosca
08:13 AM Bug #11288 (Test): Check if c3p0 is required for in-memory databases: I did port the change. Artur Școlnic
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? Artur Școlnic
06:00 AM Bug #11288: Check if c3p0 is required for in-memory databases: 11288a was merged to trunk/16471. Artur Școlnic
05:47 AM Bug #11288 (Merge Pending): Check if c3p0 is required for in-memory databases: Please merge 11288a to trunk after 11068c. Alexandru Lungu
03:56 AM Bug #11288: Check if c3p0 is required for in-memory databases: I think we can merge this one. Artur Școlnic
10:31 AM Bug #10385 (Test): Incorrect reset of the cursor cache in Reposition: Greg Shah
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. Eduard Soltan
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... Eduard Soltan

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... Ovidiu Maxiniuc
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/@. Greg Shah
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... Artur Școlnic
10:40 AM Feature #9545: confirm/add table parameter support: Committed on *9545a, rev. 16473.*
Fixed different error handling logic. Eduard Soltan

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. Ovidiu Maxiniuc
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... Artur Școlnic
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... Artur Școlnic
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... Alexandru Lungu
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... Artur Școlnic
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... Ovidiu Maxiniuc
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+. Teodor Gorghe
05:38 AM Feature #9545: confirm/add table parameter support: Changes in current form passed initial conversion and regression tests on ETF. Eduard Soltan
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... Eduard Soltan

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... Ovidiu Maxiniuc
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... Ovidiu Maxiniuc

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... Artur Școlnic
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. Teodor Gorghe
07:33 AM Bug #11288 (Review): Check if c3p0 is required for in-memory databases: Ovidiu, please review 11288a. Artur Școlnic
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... Artur Școlnic
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... Artur Școlnic
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. Teodor Gorghe
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*... Teodor Gorghe
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... Teodor Gorghe

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... Teodor Gorghe
06:17 AM Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used: Awesome!!! Greg Shah
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). Teodor Gorghe
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.... Teodor Gorghe
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... Teodor Gorghe
07:58 AM Feature #11291 (WIP): Improve h2 locking system: Artur Școlnic
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... Artur Școlnic
06:34 AM Feature #11291 (Review): Improve h2 locking system: Artur Școlnic

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... Teodor Gorghe
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... Teodor Gorghe
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 ... Teodor Gorghe
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... Alexandru Lungu
08:11 AM Bug #11288 (Test): Check if c3p0 is required for in-memory databases: Alexandru Lungu
08:07 AM Bug #10776 (Pending): FFC.touch standing out in profiling: This effort was integrated in #11037 Alexandru Lungu
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 ... Artur Școlnic
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... Artur Școlnic
07:09 AM Feature #11287 (New): Leverege the pg_prewarm function to improve cold server performance: Artur Școlnic

03/10/2026

02:08 PM Feature #9545: confirm/add table parameter support: h3. Buffer / Temp-Table explicit deletion... Eduard Soltan

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?... Roger Borrello
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... Artur Școlnic
07:40 AM Feature #9545: confirm/add table parameter support: *MyClass1.cls*... Eduard Soltan

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... Alexandru Lungu
09:52 AM Bug #11279: RecordNursery invalidated for a rollabacked transient record: *start.p*... Eduard Soltan
09:38 AM Bug #11279 (New): RecordNursery invalidated for a rollabacked transient record: Eduard Soltan

03/04/2026

12:56 PM Bug #11231 (Test): FastFindCache clear operations may leak memory: Greg Shah
09:57 AM Bug #11231: FastFindCache clear operations may leak memory: 11231a was merged to trunk/16455. Artur Școlnic
09:40 AM Bug #11231 (Merge Pending): FastFindCache clear operations may leak memory: I tested POC, everything is fine. Please proceed with merging. Alexandru Lungu
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? Artur Școlnic
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... Stefanel Pezamosca
03:40 AM Bug #11231: FastFindCache clear operations may leak memory: Unit tests of a large customer application passed. Eduard Soltan
11:15 AM Feature #4369: implement stateless FWD server clustering: Yes
Greg Shah
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 ... Roger Borrello
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... Greg Shah
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... Roger Borrello
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... Roger Borrello

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... Ovidiu Maxiniuc
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? Artur Școlnic
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... Ovidiu Maxiniuc
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... Artur Școlnic
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.
... Artur Școlnic
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... Stefanel Pezamosca
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... Eduard Soltan
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 ... Constantin Asofiei
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.... Eduard Soltan
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'. ... Constantin Asofiei
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... Eduard Soltan
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... Alexandru Lungu

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. Ovidiu Maxiniuc
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. Constantin Asofiei
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... Eduard Soltan
10:53 AM Feature #9545: confirm/add table parameter support: Is the buffer @httTest:default-buffer@ still holding the record when @OutputTableHandleCopier@ is copied? Constantin Asofiei
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... Eduard Soltan
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*... Constantin Asofiei
10:43 AM Feature #9545: confirm/add table parameter support: start.p... Eduard Soltan
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... Artur Școlnic
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... Greg Shah
09:51 AM Bug #11161: fail gracefully when the database connection can not be established: Do nested blocks like this:... Constantin Asofiei
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... Artur Școlnic
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... Greg Shah
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 ... Artur Școlnic
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... Artur Școlnic
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 ... Artur Școlnic
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? Greg Shah
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:
... Artur Școlnic

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » Database

Activity

Activity

03/26/2026

03/25/2026

03/23/2026

03/20/2026

03/19/2026

03/18/2026

03/17/2026

03/16/2026

03/14/2026

03/13/2026

03/12/2026

03/11/2026

03/10/2026

03/09/2026

03/05/2026

03/04/2026

03/03/2026

03/02/2026

02/27/2026

02/26/2026

02/25/2026