Activity

From 06/01/2026 to 06/30/2026

06/30/2026

09:15 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Testing done for 11573a:
Multi tenant application: harness, performance and reports
Large gui application: unit tes... Artur Școlnic
08:18 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Constantin Asofiei wrote:
> * What if you do a DO TRANSACTION (a sub-tx) in @proc0@?
no effect, just one savepoint ... Artur Școlnic
07:47 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Artur Școlnic wrote:
> Oh, I was using the implicit buffer for the assign, not b-book.
> Anyway, the behavior is th... Constantin Asofiei
07:46 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Oh, I was using the implicit buffer for the assign, not b-book.
Anyway, the behavior is the same, there is only one ... Artur Școlnic
07:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: I used an inner procedure. Will test with an external one. Artur Școlnic
07:37 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Artur Școlnic wrote:
> The procedure cannot update the record since the buffer has a no-lock. Seems like the trigger... Constantin Asofiei
07:35 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Constantin Asofiei wrote:
> in the mean time, please test:
> * what happens if you remove the trigger
Only one s... Artur Școlnic
07:05 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Validation.flush
The described failure path is not quite right, when flushImpl fails, it rolls back its own savepoi... Artur Școlnic
06:14 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: > Should i address those findings?
Please cross-check them. I will do a separate individual review my own. If you ... Alexandru Lungu
06:13 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Artur Școlnic wrote:
> Can I continue testing?
Yes, but in the mean time, please test:
* what happens if you remov... Constantin Asofiei
06:10 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Sorry, that was supposed to be a question :)
Should i address those findings? Artur Școlnic
06:08 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Alex,
If you agree with those points, I will fix the issues AI found. Artur Școlnic
06:06 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Artur, some AI observations:
* *[MAJOR]* _functional_ @Validation@.@flush@: @dmlSavepoint.complete()@ runs after t... Alexandru Lungu
05:50 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Can I continue testing? Artur Școlnic
05:40 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: start.p... Artur Școlnic
04:40 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: No, I will come up with one. Artur Școlnic
04:39 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Artur, do you have a standalone test which shows how these changes are used? Constantin Asofiei
04:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Changed priority to reflect the urgency of the fix. Artur Școlnic
03:42 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Thank you, Ovidiu.
I will start testing while Constantin looks over the changes. Artur Școlnic

06/29/2026

06:37 PM Bug #11573: Remove unnecessary JDBC savepoint during validation: I have reviewed 11573a, 16622..16624. I think the solution might work.
Please fix the following code style issues... Ovidiu Maxiniuc
08:29 AM Bug #11573 (Review): Remove unnecessary JDBC savepoint during validation: Ovidiu, Constantin,
The changes in rev 16624 are as follows:
Undoable DMO changes are still tracked immediately in... Artur Școlnic
08:03 AM Bug #11573 (WIP): Remove unnecessary JDBC savepoint during validation: Ovidiu, I saw that we eagerly set savepoints for undoable tracking, I am trying to improve that, please postpone the ... Artur Școlnic
02:16 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Ovidiu, please take a look again at rev 16623. Artur Școlnic
09:48 AM Bug #11569 (Review): Implement a finer grained invalidation for FastFindCache: Alexandru,
The changes in 11569a are meant to:
Reduce unnecessary ffcache invalidation by retaining results that a... Artur Școlnic
09:30 AM Bug #11576 (Review): Fix outer-join iteration handling for nullOuter.: ... Stefanel Pezamosca

06/26/2026

08:37 AM Bug #11576 (Internal Test): Fix outer-join iteration handling for nullOuter.: I will upload @CompoundOuterJoinTest.cls@ to testcases project after I add few more variations.
*10803a* was rebas... Stefanel Pezamosca
08:01 AM Bug #11576: Fix outer-join iteration handling for nullOuter.: This task covers the remaining outer-join query iteration issues that are not fixed by 10962a.
#10962 should addre... Stefanel Pezamosca
08:01 AM Bug #11576 (Review): Fix outer-join iteration handling for nullOuter.: Stefanel Pezamosca
07:12 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Alexandru Lungu wrote:
> PS: My comment was to remind of the origin for this savepoint. Radu, do you recall the task... Radu Apetrii
05:52 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: PS: My comment was to remind of the origin for this savepoint. Radu, do you recall the task in which this happened? T... Alexandru Lungu
05:51 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: > I will change Validation.flush() so it only creates the validation savepoint when there is actual DML pending.
T... Alexandru Lungu
02:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Ovidiu,
You are right, I think the fix is to first short circuit clean, already-persisted records. Then fire the tr... Artur Școlnic
08:32 PM Bug #11573: Remove unnecessary JDBC savepoint during validation: My first question is what happens if the trigger decides to reject the record using <code class="PHP">RETURN ERROR</c... Ovidiu Maxiniuc
07:04 AM Bug #10962 (WIP): Optimized multi-table compound components are not invalidated: Branch 10962a was merged to trunk rev 16623 and archived.
This is opened for assessing potential performance impro... Alexandru Lungu
07:00 AM Bug #10962 (Merge Pending): Optimized multi-table compound components are not invalidated: POC testing passed.
ETF testing passed.
Preparing to merge. Alexandru Lungu
09:56 PM Feature #10491: Tool to standardize PG cluster creation: Ovidiu Maxiniuc wrote:
> After re-reviewing the script in r16624 I did not see anything wrong, except:
> * the depe... Roger Borrello

06/25/2026

07:55 PM Feature #10491: Tool to standardize PG cluster creation: After re-reviewing the script in r16624 I did not see anything wrong, except:
* the dependency on @startup_pg.sh@. T... Ovidiu Maxiniuc
10:16 AM Feature #10491: Tool to standardize PG cluster creation: I rebased *10491a* and verified @fwd_create_pg_cluster.sh@ matches up with the lastest from the *container* project. ... Roger Borrello
01:52 PM Bug #11573: Remove unnecessary JDBC savepoint during validation: Ovidiu, please also take a look. Changes make sense for me. Constantin Asofiei
01:48 PM Bug #11573 (Review): Remove unnecessary JDBC savepoint during validation: I committed the solution to 11573a, in the end it was a corner case where a trigger flushed and validated a record, t... Artur Școlnic
09:38 AM Bug #11573 (WIP): Remove unnecessary JDBC savepoint during validation: Artur Școlnic
09:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation: Profiling a client's application write heavy scenario showed that we are setting and immediately releasing savepoints... Artur Școlnic
09:33 AM Bug #11573 (Test): Remove unnecessary JDBC savepoint during validation: Artur Școlnic
05:02 AM Bug #11502 (Internal Test): Recycle dirty share H2 session: Teodor, I'm OK with the changes. Please rebase and also test with #10614 app. Constantin Asofiei
04:57 AM Bug #11502 (Review): Recycle dirty share H2 session: Teodor Gorghe
04:57 AM Bug #11502 (WIP): Recycle dirty share H2 session: Committed revision *16600* on task branch *11502a*:
* Pool H2 dirty-share database connection.
*Constantin*, plea... Teodor Gorghe
04:49 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Smoke testing and stress testing of a customer app with 11526a did not reveal any regressions. Razvan-Nicolae Chichirau

06/24/2026

10:39 AM Bug #11569: Implement a finer grained invalidation for FastFindCache: This issue is dedicated to optimizing the FFC invalidation, specifically the full index/table invalidation that can b... Artur Școlnic
10:35 AM Bug #11569 (WIP): Implement a finer grained invalidation for FastFindCache: Artur Școlnic
10:34 AM Bug #11569 (Review): Implement a finer grained invalidation for FastFindCache: Artur Școlnic
04:06 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Performance for the #11477 scenario (with added 0.5ms latency) is ... Artur Școlnic

06/23/2026

02:45 PM Feature #11526 (Internal Test): Implement in-memory uniquness validation using Bloom filters: Very well!
Let's get it tested and profiled, to see if it works correctly and improves performance, not regress it. Ovidiu Maxiniuc
12:39 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I addressed the other concerns, Ovidiu, please review rev 16611. Artur Școlnic
12:26 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Ovidiu Maxiniuc wrote:
> * @BloomFilterHashUtils.java@
> ** line 159: I still think this is *not correct*: notice... Artur Școlnic
04:47 AM Bug #10962: Optimized multi-table compound components are not invalidated: Alexandru Lungu wrote:
> Stefanel, please help with testing:
>
> * please test the other application REST API tes... Stefanel Pezamosca

06/22/2026

04:51 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16609+
I think you are on the right track. The issues previously reported look fixed. I see ot... Ovidiu Maxiniuc
09:18 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: I made the changes, now the filters are initialized async on the first validation, until it is fully initialized, it ... Artur Școlnic
06:14 AM Bug #10962 (Internal Test): Optimized multi-table compound components are not invalidated: > Hmm, I think that query.getTableCount() == 1 && limitation can be lifted, in order to avoid setting the reference r... Alexandru Lungu

06/18/2026

03:59 PM Bug #11552: Stale data with write trigger.: Ovidiu Maxiniuc wrote:
> The @doBlock@ itself will not mark the record as @STALE@, just @CHANGED@. Clearly, a secon... Eduard Soltan
03:35 PM Bug #11552: Stale data with write trigger.: I tried to track it back, but something is missing. A link.
The @doBlock@ itself will not mark the record as @STAL... Ovidiu Maxiniuc
02:33 PM Bug #11552: Stale data with write trigger.: Constantin Asofiei wrote:
> Eduard, do you have a standalone test for this? Or these are just observations from deb... Eduard Soltan
02:03 PM Bug #11552: Stale data with write trigger.: Eduard, do you have a standalone test for this? Or these are just observations from debugging? Constantin Asofiei
11:46 AM Bug #11552: Stale data with write trigger.: Lets suppose we will have a buffer scoped to transactional block. As finalizables of this block the will be register... Eduard Soltan
11:18 AM Bug #11552 (New): Stale data with write trigger.: Eduard Soltan

06/17/2026

08:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, rebuild the index at FWD server must be done concurrently (the runtime will work without the filter, and the f... Constantin Asofiei
08:53 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: Artur Școlnic
08:52 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Ok, I was reluctant to go with this approach since it would cripple the server on startup for an undetermined amount ... Artur Școlnic
07:44 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur Școlnic wrote:
> > * consistency - always rebuilt on server startup, while feeding records from the database t... Constantin Asofiei
07:38 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Constantin Asofiei wrote:
> * degradation - there are cases where a physical table is used as a temp-table - data is... Artur Școlnic
07:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: If you have an early implementation, we need some serious stress-testing, for 100s of millions of records, where mult... Constantin Asofiei
07:13 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, these are some notes after having a discussion with Ovidiu:
* degradation - there are cases where a physical ... Constantin Asofiei
04:37 AM Feature #6720: lazy hydration: Committed with the fix for #6720-179 in +6720b/r16636+. Teodor Gorghe

06/16/2026

05:30 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16607+
*I.* I see you have radically changed the way the hash is computed. I see it is closer ... Ovidiu Maxiniuc
09:21 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: Ovidiu Maxiniuc wrote:
> ** lines 311, 342: not having default values will make configuration difficult. What shou... Artur Școlnic
08:37 PM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: +Review of 11526a, r16500..16606+
* @Validation.java@
** lines 151-153: the imports should use the .* syntax (pac... Ovidiu Maxiniuc
10:21 AM Feature #10436: Detect Sequential Data Access and Prefetch Records from the Database: We could detect at runtime and record hints based on this. Those hints could then change how we convert. Greg Shah
09:25 AM Feature #10436: Detect Sequential Data Access and Prefetch Records from the Database: I finished a prototype implementation, it detects when a find unique query is being iterated, meaning that the same s... Artur Școlnic
05:35 AM Bug #11502: Recycle dirty share H2 session: Generally speaking I would expect the dirty db to be less strained than the primary one due to the limited scope of t... Artur Școlnic
05:28 AM Bug #11502: Recycle dirty share H2 session: I don't think cloning *shared primary db* / *tenant primary db* config because of #11502-12.
Dirty DB connections ... Teodor Gorghe
04:50 AM Bug #11502: Recycle dirty share H2 session: Teodor, the shared db has a directory config, it can be used for the dirty shared db. The tenant private databases ha... Artur Școlnic
04:47 AM Bug #11502: Recycle dirty share H2 session: A quick reminder about the question from #11502-12.
#11502 is not a critical issue, but the performance is a bit w... Teodor Gorghe
04:00 AM Feature #6720: lazy hydration: Committed revision *16635* on task branch *6720b*:
* Implemented runtime feedback field usage feature which decides ... Teodor Gorghe
02:36 AM Feature #6720: lazy hydration: Rebased *6720b* to trunk rev *16603*. Latest revision is *16632*.
A copy of old *6720b* is in @devsrv01:/tmp/tg.2026... Teodor Gorghe

06/15/2026

07:11 AM Feature #6720: lazy hydration: Ok, I am starting to rebase this branch.
I have tried to reproduce what you told in previous discussions, two @FOR... Teodor Gorghe
06:36 AM Feature #6720: lazy hydration: > Alexandru/Greg, should I rebase 6720b to latest trunk revision or should I port these to a new branch?
Please r... Alexandru Lungu
04:14 AM Feature #6720: lazy hydration: *Alexandru/Greg*, should I rebase *6720b* to latest trunk revision or should I port these to a new branch?
I have ... Teodor Gorghe
03:59 AM Feature #6720: lazy hydration: I think #10554 fix relevant here because there are more @Session.associate@ calls.
There is a bug with this testca... Teodor Gorghe
01:50 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: 11526a can be reviewed. The implemented features are:
1. Filter population and persistence as a separate ant task
2... Artur Școlnic

06/12/2026

09:03 AM Feature #6720: lazy hydration: Alexandru Lungu wrote:
> Well, if you have a result-set and do 3 next operations, the first two rows are lost. If yo... Teodor Gorghe
08:31 AM Feature #6720: lazy hydration: Again, let's back up here and understand what is the case for 4GL code to access to a specific row's results after it... Greg Shah
08:07 AM Feature #6720: lazy hydration: > This would be outside of the PRESELECT. If the buffers used for a PRESELECT query can't be accessed outside of thei... Alexandru Lungu
07:50 AM Feature #6720: lazy hydration: > If a FIND is executed and the FFC is used, then the id provided. The id is checked against the session cache. The s... Greg Shah
07:43 AM Feature #6720: lazy hydration: Alexandru Lungu wrote:
> The fundamental difference between trunk and #6720 is that the session cached DMOs may get ... Teodor Gorghe
07:30 AM Feature #6720: lazy hydration: > I'm not sure I agree on the PRESELECT. I'd like to know what the real cases are where we have to load the DMO after... Alexandru Lungu
06:24 AM Feature #6720: lazy hydration: Greg Shah wrote:
> Is the current implementation handling things like @OPEN QUERY@/@GET@, all scenarios that use thi... Teodor Gorghe
06:21 AM Feature #6720: lazy hydration: I'm not sure I agree on the @PRESELECT@. I'd like to know what the real cases are where we have to load the DMO afte... Greg Shah
05:45 AM Feature #6720: lazy hydration: > We should expand this much further as a first step. After that, we can look at optimizations to minimize cases wher... Alexandru Lungu
04:07 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... Teodor Gorghe
08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I changed the config to be read from directory, each database will have it's config under @database/db_name/orm/bloom... Artur Școlnic
06:41 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: When a record is added, we hash its indexed fields and set the corresponding bits to 1. Those bits may already be sha... Artur Școlnic
06:22 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I'm surprised that the solution doesn't just clear the bits associated with the deleted record. Greg Shah
06:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> So there will be a "buildup" of invalid (out of date) bits for deleted records?
Yes, but a spa... Artur Școlnic
06:13 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: So there will be a "buildup" of invalid (out of date) bits for deleted records? That is even more of a reason to re-... Greg Shah
02:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: A bloom filter is not meant to register a deleted record, there is a separate structure called counting bloom filter ... Artur Școlnic

06/11/2026

03:43 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, a more technical question:
The Bloom data structure is inherently additive, you set/add bits as the hashes ar... Ovidiu Maxiniuc
10:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The implementation is at a point where a customer project could be tested fully, I will get on with that and deffer f... Artur Școlnic
09:24 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Constantin Asofiei wrote:
> Artur, some questions:
> * for a running FWD server, when does this gets persisted on d... Artur Școlnic
09:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> I like the non-persisted nature of the design in #11526-27.
I like it too, unless the population... Artur Școlnic
08:40 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I like the non-persisted nature of the design in #11526-27.
I don't think we can apply changes to the filter befor... Greg Shah
08:37 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur, some questions:
* for a running FWD server, when does this gets persisted on disk? Can it recover in case th... Constantin Asofiei
08:32 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: > This is a level of speed that means we don't need to persist things in between server restarts. We could just build... Alexandru Lungu
08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: For now, make the location of the cache configurable. Production deployments must carefully place and secure all fil... Greg Shah
08:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: As far as memory consumption for the same 10 tables with 7mil rows goes, these are the values
if all where in the sm... Artur Școlnic
07:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> This is a level of speed that means we don't need to persist things in between server restarts. ... Artur Școlnic
07:53 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: This is a level of speed that means we don't need to persist things in between server restarts. We could just build ... Greg Shah
07:48 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I tested the filter population on a customer db, I used 10 tables with 7.2 mil rows in total, the filters took only 1... Artur Școlnic
07:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: When it comes to security, the filters have no readable data, it is hashed and highly compressed. The more concerning... Artur Școlnic
07:29 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The easiest and most performant way is to store the artifacts (serialized filters) on the server filesystem, for dist... Artur Școlnic
07:23 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: My point is that this should be a general solution not something hard coded to multi-tenant.
Yes, you can read the... Greg Shah
07:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Greg Shah wrote:
> I don't understand why this would be associated with tenant data. This is a general solution for... Artur Școlnic
06:45 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I don't understand why this would be associated with tenant data. This is a general solution for persistence, right?... Greg Shah
06:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I actually intended to use an external file. Adding tenant API for filter management is the better and more elegant s... Artur Școlnic
06:28 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Artur Școlnic wrote:
> I just realized that tenant API needs a running server, I think as a first option, manually w... Greg Shah
05:49 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I just realized that tenant API needs a running server, I think as a first option, manually writing all the database ... Artur Școlnic
05:34 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I need a way to specify what tables need to use the filters and what config to apply to them, since filter population... Artur Școlnic
07:48 AM Bug #11502: Recycle dirty share H2 session: There is a list of @c3p0@ parameters which should not be copied from primary database, like @minPoolSize@, @initialPo... Teodor Gorghe

06/10/2026

06:31 PM Bug #11529: Incorrect Data Structure for TenantManager: This is an issue I am thinking for some time now. It is not critical, but only because the single client using a MT-e... Ovidiu Maxiniuc
06:02 PM Bug #11529 (New): Incorrect Data Structure for TenantManager: Ovidiu Maxiniuc
10:03 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Added artifact persistence, initialization from db, support for an Ant task. The code needs proper formatting and jav... Artur Școlnic
08:18 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: I am planning to execute the filters initialization as Ant task, it would need to be executed after the import, stric... Artur Școlnic
03:16 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: The structure is a bit array, a very large one, 5 million for example. On write the indexed fields are hashed a few t... Artur Școlnic
08:33 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > Until now, the lazy hydration is done just for three things:
>
> We should expand this much ... Teodor Gorghe
06:44 AM Feature #6720: lazy hydration: > Until now, the lazy hydration is done just for three things:
We should expand this much further as a first step.... Greg Shah
05:40 AM Feature #6720: lazy hydration: I have started to partially implement *Runtime feedback per call-site*, with the key set to @(database, fql)@.
{{C... Teodor Gorghe
03:04 AM Feature #6720: lazy hydration: Greg Shah wrote:
> I wonder if we have minimized the hydration needed? My understanding is that previous attempts a... Teodor Gorghe
01:58 AM Feature #6720: lazy hydration: Greg Shah wrote:
> > I have made these measurements because I need to know if fixing the performance findings, but I... Teodor Gorghe
01:12 AM Feature #6720: lazy hydration: Ovidiu Maxiniuc wrote:
> Teodor,
> I had a quick look at the patch you posted in #6720-159. What I immediately not... Teodor Gorghe
07:14 AM Bug #11288: Check if c3p0 is required for in-memory databases: 11288d was ported to 10614_main rev 16417. Artur Școlnic
06:53 AM Bug #11288: Check if c3p0 is required for in-memory databases: Artur, please patch 10614_main with 11288a now. Constantin Asofiei

06/09/2026

06:47 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Sorry to play the devil's advocate.
I understand that the data structure is some kind of SQL index, mapping from ... Ovidiu Maxiniuc
10:09 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Alexandru Lungu wrote:
> This is a red flag for me. We are talking about tens of millions of record. This may requir... Artur Școlnic
09:56 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: > on initialization all records are read from the db,
This is a red flag for me. We are talking about tens of mill... Alexandru Lungu
09:36 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Ovidiu, the new approach is much simpler than that. The initialized filters hold only bits, some of them are set base... Artur Școlnic
09:29 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters: This is definitely a new approach.
Some notes in this regard:
* at 'in-memory' level, we already have @UniqueTrac... Ovidiu Maxiniuc
09:19 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: Committed the initial version, so far it supports only in memory insertion/filter population and lookup, the filters ... Artur Școlnic
04:15 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters: A Bloom filter is a space-efficient probabilistic data structure used to quickly test whether an item has been seen b... Artur Școlnic
04:05 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters: Artur Școlnic
10:49 AM Feature #6720: lazy hydration: > I have made these measurements because I need to know if fixing the performance findings, but I think I shall find ... Greg Shah
10:43 AM Feature #6720: lazy hydration: Teodor,
I had a quick look at the patch you posted in #6720-159. What I immediately noticed is that it rolls back R... Ovidiu Maxiniuc
08:41 AM Feature #6720: lazy hydration: I have done some tests *6720b* vs *trunk* and these are the measurements:
|_. scenario |_. rows |_. fields |_. 4GL (... Teodor Gorghe
03:20 AM Feature #6720: lazy hydration: This is the list of findings for a patch which I am using (based on *6720b*):
{{Collapse(Findings)
h1. Code Review ... Teodor Gorghe
03:34 AM Bug #11502: Recycle dirty share H2 session: It is good, but the used config for the data sources is the default one, it needs to use the tenant specific one to a... Artur Școlnic
03:30 AM Bug #11502: Recycle dirty share H2 session: Can you take into the patch? Is a reasonable change? Teodor Gorghe
03:29 AM Bug #11502: Recycle dirty share H2 session: If it helps a customer application, I am ok with adding it back, just make sure to inherit the configuration of the d... Artur Școlnic
03:25 AM Bug #11502: Recycle dirty share H2 session: Artur Școlnic wrote:
> Connection pooling was removed for the Meta and Dirty databases to simplify configuration and... Teodor Gorghe
03:07 AM Bug #11502: Recycle dirty share H2 session: Connection pooling was removed for the Meta and Dirty databases to simplify configuration and improve maintainability... Artur Școlnic

06/08/2026

06:06 AM Bug #11502: Recycle dirty share H2 session: Artur, can you explain your changes for #11288 regarding dirty database?
I think the easiest way to fix the perfor... Teodor Gorghe

06/03/2026

04:29 AM Bug #9194 (WIP): FWD selects the wrong index when using CONTAINS?: False alarm, it seems that the selected index is wrong even with the recent trunk. The discussion happened in #11448. Radu Apetrii
04:03 AM Bug #9194 (Test): FWD selects the wrong index when using CONTAINS?: Radu Apetrii

« Previous

Also available in: Atom

Project

General

Profile

FWD » Core Development » Database

Activity

Activity

06/30/2026

06/29/2026

06/26/2026

06/25/2026

06/24/2026

06/23/2026

06/22/2026

06/18/2026

06/17/2026

06/16/2026

06/15/2026

06/12/2026

06/11/2026

06/10/2026

06/09/2026

06/08/2026

06/03/2026