Activity
From 06/27/2026 to 07/26/2026
Today
- 09:07 AM Feature #5219: implement native full-text search for word index and CONTAINS support
- The @to_tsquery()@ and @to_tsvector()@ have a first parameter that _configures_ how the word split is performed. Curr...
- 08:37 AM Feature #5219: implement native full-text search for word index and CONTAINS support
- I don't think PostgreSQL @to_tsvector@ splits words in the same way as OE does. But I'm thinking if we can use @array...
- 07:15 AM Feature #5219: implement native full-text search for word index and CONTAINS support
- For FTS support, we have @to_tsvector@ in PostgreSQL to get the 'words'; does this split into words in the same way a...
- 08:42 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Artur Școlnic wrote:
> Yes, but for the purpose of this task, I think it is reasonable to test with batch size 1, I ... - 08:40 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Yes, but for the purpose of this task, I think it is reasonable to test with batch size 1, I doubt the performance hi...
- 08:39 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Constantin Asofiei wrote:
> No, I mean if the maxPoolSize is set to a limit close to max_connection, and you have N ... - 08:36 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Artur Școlnic wrote:
> Wait, if you meant that the maxpoolsize will be exceeded because of the batch, than the answe... - 08:33 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Wait, if you meant that the maxpoolsize will be exceeded because of the batch, than the answer is no.
- 08:31 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Yes, but if a large number of connections are required to be acquired by the pool, this will perform worse than with ...
- 08:27 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Artur Școlnic wrote:
> The connections are acquired in batches configurable by the user.
So what is 'in use' and al... - 08:25 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- The connections are acquired in batches configurable by the user.
- 08:22 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Eduard Soltan wrote:
> As a follow up to the today's meet discussion, I think some other thing that we could do is t... - 08:20 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- As a follow up to the today's meet discussion, I think some other thing that we could do is to impose a logical trash...
- 04:20 AM Feature #11467 (Test): Improve ImportWorker performance
- trunk/16665 was ported to @10614_main@ rev 16433.
- 04:13 AM Feature #11467: Improve ImportWorker performance
- Branch *11467a* was merged into trunk as rev. *16665* and archived.
Porting to @10614_main@. - 04:04 AM Feature #11467 (Merge Pending): Improve ImportWorker performance
- 03:54 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> It uses the same @DataFileReader@ as with trunk, sets the code page for the words function, @... - 03:06 AM Feature #11467: Improve ImportWorker performance
- It uses the same @DataFileReader@ as with trunk, sets the code page for the words function, @BulkCopyCsvWriter@ uses ...
- 02:42 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> I have tested the runtime on some converted apps (ETF, 10614 app and 8755 app) and it seems O... - 02:39 AM Feature #11467: Improve ImportWorker performance
- I have tested the runtime on some converted apps (ETF, 10614 app and 8755 app) and it seems OK.
Do we need tests o... - 02:37 AM Feature #11467: Improve ImportWorker performance
- Teodor, do we need any more testing?
- 01:06 AM Feature #11467: Improve ImportWorker performance
- Done in +11467a/r16569+.
- 01:51 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Ovidiu Maxiniuc wrote:
> I see nothing wrong with the update. Cool!
Thank you!
> I see the %Done is still at 60. A...
07/21/2026
- 05:55 PM Feature #11526 (Internal Test): Implement in-memory uniquness validation using Bloom filters
- I see nothing wrong with the update. Cool!
I see the %Done is still at 60. Are there some other thing to implement... - 09:54 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- Ovidiu, thank you for the feedback, please take a look at rev 16613.
- 02:02 PM Feature #11467 (Internal Test): Improve ImportWorker performance
- +Review of 11467a / r 16568+
I do like the new code. I think it is more readable. You addressed some of the issues... - 11:18 AM Feature #11467: Improve ImportWorker performance
- Constantin Asofiei wrote:
> Eric, any other concerns?
Let's be sure to include multi-tenant in the testing.
O... - 03:01 AM Feature #11467 (Review): Improve ImportWorker performance
- Eric, any other concerns?
*Ovidiu* - please take at the changes again (moved to review for better visibility). - 12:36 PM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- Committed on *11633a, rev. 16659*.
ConnectionBudgetManager manages connection buget per physical instance, keyed b... - 09:55 AM Feature #11638 (Review): Reduce FastFindCache invalidation thrashing
- Constantin, when you have the time, please review 11638a.
- 07:10 AM Feature #11638: Reduce FastFindCache invalidation thrashing
- The initial implementation shows promise, these are the results of comparing memory retention of FFC, trunk vs 11638a...
- 05:17 AM Feature #11638 (WIP): Reduce FastFindCache invalidation thrashing
- 05:17 AM Feature #11638: Reduce FastFindCache invalidation thrashing
- @FastFindCache@ currently reacts to writes by invalidating cached results very aggressively. In a workload where the ...
- 05:12 AM Feature #11638 (Review): Reduce FastFindCache invalidation thrashing
07/20/2026
- 06:03 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- +Review of 11526a/r16612+
I found only small issue in a single source file from the changeset:
* @FilterManager.j... - 10:06 AM Feature #11526 (Review): Implement in-memory uniquness validation using Bloom filters
- Implemented the memory management in rev/16612, Ovidiu, please review.
- 09:10 AM Bug #11573 (Test): Remove unnecessary JDBC savepoint during validation
- 11573b was merged to trunk/16658 and 10614_main/16432.
- 08:55 AM Bug #11573 (Merge Pending): Remove unnecessary JDBC savepoint during validation
- 11573b can be merged now.
07/18/2026
- 02:08 AM Feature #11467: Improve ImportWorker performance
- Worth taking a note is that with *11467a*, there are larger gaps between *recid*, which happens on the following case...
- 01:45 AM Feature #11467: Improve ImportWorker performance
- Eric Faulhaber wrote:
> I haven't reviewed the code, so this may not be a relevant inquiry, but please confirm:
>
...
07/17/2026
- 05:05 PM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> SQL dump gives output difference every time when you import from database, due to the fact ho... - 03:02 PM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> Done in +11467a/r16568+.
Ovidiu, please review again. - 10:23 AM Feature #11467: Improve ImportWorker performance
- Done in +11467a/r16568+.
- 10:03 AM Feature #11467: Improve ImportWorker performance
- I see this from claude, it may be a valid point:
> * *[MINOR]* _functional_ @ImportWorker@.@importTable@ (bulk path)... - 07:21 AM Feature #11467: Improve ImportWorker performance
- Tested *10614_main* to import the database. Import time has reduced with nearly 50%.
Committed revision *16567* on... - 05:32 AM Feature #11467: Improve ImportWorker performance
- Currently working on #7143-1977, but I think it will be ready EOD.
- 05:31 AM Feature #11467: Improve ImportWorker performance
- Let me know if and when the branch is ready to merge.
- 03:16 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> Constantin Asofiei wrote:
> > Teodor, please also test a (small) import with 10614_main.
> ... - 03:15 AM Feature #11467: Improve ImportWorker performance
- Constantin Asofiei wrote:
> Teodor, please also test a (small) import with 10614_main.
On that app, we don't have... - 03:14 AM Feature #11467: Improve ImportWorker performance
- Teodor, please also test a (small) import with 10614_main.
- 02:56 AM Feature #11467: Improve ImportWorker performance
- Addressed code review #11467-17 in +11467a/r16566+.
- 01:55 AM Feature #11467: Improve ImportWorker performance
- SQL dump gives output difference every time when you import from database, due to the fact how data is being stored i...
- 08:27 AM Feature #11526 (WIP): Implement in-memory uniquness validation using Bloom filters
- Even for preview, it needs to be workable for multi-tenant. Let's keep going on improvements before merge.
- 07:31 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- For memory management I am implementing 3 things:
1. Making filter sizing table-specific instead of one fixed medium... - 07:20 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- I am ok with presenting this feature as a prototype for now, which is easily disabled, but certainly not as a finishe...
- 07:10 AM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- The current implementation is not suited for a multi tenant env, the memory consumption will be too high. I need to i...
07/16/2026
- 12:42 PM Feature #11467: Improve ImportWorker performance
- I think that is a pass.
However, if you want to do a cross-check you can do a SQL database dump (backup) in text (SQ... - 12:37 PM Feature #11467: Improve ImportWorker performance
- That is expected since the dump as imported would be in 8859-1 and the database as imported is UTF-8. The import tra...
- 12:02 PM Feature #11467: Improve ImportWorker performance
- Greg Shah wrote:
> Use our export tool to dump the content to @.d@ and then compare the @.d@ files to the originals.... - 09:27 AM Feature #11467 (Internal Test): Improve ImportWorker performance
- 09:27 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> Ovidiu, can you review +11467a/r16565+. Thanks!
+Review of 11467a / r16565+
I think the... - 07:38 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> I am finding a way to validate the import on a *41GB* dump.
Use our export tool to dump th... - 06:16 AM Feature #11467: Improve ImportWorker performance
- I am finding a way to validate the import on a *41GB* dump.
- 06:08 AM Feature #11467: Improve ImportWorker performance
- I've ran the import with the #8755 18GB data dump (as I still have previous logs), and:
* 8755d import
> 100.00000%... - 05:43 AM Feature #11467: Improve ImportWorker performance
- Constantin Asofiei wrote:
> I would have expected a greater improvement than just ~25%.
I think I have a high s... - 05:34 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> *CLOB* data type is using @COPY@ statement, there is no issue regarding that. I have gated *B... - 05:31 AM Feature #11467: Improve ImportWorker performance
- When running @ant import.db@, @clean.db@ is being executed, which drops the database.
Word-index triggers are being ... - 05:20 AM Feature #11467: Improve ImportWorker performance
- Teodor Gorghe wrote:
> I have done a couple of fixes, most of them were style fixes, support of COPY for word index ... - 05:01 AM Feature #11467: Improve ImportWorker performance
- Some measurements done on two projects, one with a smaller dump and another one, with way larger dump.
Project 1:
... - 04:58 AM Feature #11467 (Review): Improve ImportWorker performance
- 04:58 AM Feature #11467 (WIP): Improve ImportWorker performance
- 04:58 AM Feature #11467: Improve ImportWorker performance
- I have done a couple of fixes, most of them were style fixes, support of COPY for word index tables, tuned *ImportWor...
- 10:39 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- max_connections is 'per cluster'. This needs to consider the max_connections for that cluster, and group these value...
- 10:35 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- I like this a lot. In order to handle load balancing and the natural variability of the number of tenant sessions pe...
- 09:59 AM Support #11633: Reduce manual c3p0 tuning burden across cluster scale changes
- One idea could be:
Configure a single cluster-wide connection budget per physical database instead, and let each ... - 09:56 AM Support #11633 (New): Reduce manual c3p0 tuning burden across cluster scale changes
- 10:25 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I don't think so, as Alex said in #11625, only keeping track of the dmo state is not enough, there are RecordNursery ...
- 10:10 AM Bug #11573 (Internal Test): Remove unnecessary JDBC savepoint during validation
- Yes, the remaining changes from 11573b are a subset of the previous revision. The removed changes have potential. Wil...
- 04:26 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I reverted some of the fixes for tests failing in trunk as they are incomplete and out of scope, Ovidiu, please revie...
07/15/2026
- 03:08 PM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> I fixed the regressions and some issues in trunk, details in #11625. I did a bit of a rework ... - 10:55 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I checked and this does not make much sense in 4gl also...
- 10:43 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- You are right, if the flush fails, the delete fails also. I will look for another solution.
- 10:00 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur, about the "flush before delete" - I think this may be problematic. The change exists only in memory until flu...
- 09:42 AM Bug #11573 (Review): Remove unnecessary JDBC savepoint during validation
- I fixed the regressions and some issues in trunk, details in #11625. I did a bit of a rework so the changes are bette...
- 03:49 AM Bug #11573 (WIP): Remove unnecessary JDBC savepoint during validation
- There are some regressions in tests Constantin provided in #11625, working on a fix.
- 02:45 PM Feature #11526: Implement in-memory uniquness validation using Bloom filters
- We need to move this ahead. If this is disabled by default, is it safe to merge?
- 02:50 AM Feature #9545: confirm/add table parameter support
- Rebased to trunk rev. 16656.
- 02:36 AM Feature #9545: confirm/add table parameter support
- Eduard, please rebase again and I'll move to full review and testing.
07/14/2026
- 01:08 PM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Ovidiu, thank you for catching these, I addressed the issues in rev 16647, please take a look again.
- 12:54 PM Bug #11573: Remove unnecessary JDBC savepoint during validation
- +Review of 11573b / r16646+
I was interested in balancing of the savepoints because of another task and I had a lo... - 11:43 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Actually, I'm in progress of doing it.
- 11:42 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Ovidiu: please review also.
- 11:26 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I can do another 2 projects besides etf. I will also ask for help with chui regression testing. If the review is posi...
- 11:19 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- What additional testing does this need, once it is reviewed?
- 08:51 AM Bug #11573 (Review): Remove unnecessary JDBC savepoint during validation
- The problem was that rollback condition in SavepointManager.rollback() was too broad, trying to compensate for the fa...
- 03:43 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Yes, this is regressed by 11573b, thank you very much, Constantin.
07/13/2026
- 05:21 PM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Eduard, I think this is the recreate for the regression in 11573b:...
- 11:35 AM Feature #1585 (Closed): add conversion and runtime support for word indexes
- 11:34 AM Feature #5219: implement native full-text search for word index and CONTAINS support
- The idea of this task is to leverage the native database full-text-search capability. It could be implemented for on...
- 08:57 AM Feature #5220 (Closed): extend word index support to SQL Server
07/08/2026
- 11:09 AM Bug #11573 (WIP): Remove unnecessary JDBC savepoint during validation
- 11573a was merged to trunk/16643 and custom branch rev 16429.
- 09:50 AM Bug #11573 (Merge Pending): Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> I tested the multi tenant project, large gui application unit tests and etf, all passed.
You... - 09:45 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I tested the multi tenant project, large gui application unit tests and etf, all passed.
07/07/2026
- 08:46 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> Done. Now 11573b contains all the changes and I will continue working on it, but 11573a conta... - 08:30 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Done. Now 11573b contains all the changes and I will continue working on it, but 11573a contains only the trigger rel...
- 08:24 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> Constantin,
> The regression in ETF comes from the second set of changes, but rev 16622-166... - 08:12 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Constantin,
The regression in ETF comes from the second set of changes, but rev 16622-16623 addresses one of the is... - 02:34 AM Bug #11502: Recycle dirty share H2 session
- Artur tested with this branch and he confirmed that the testing on #10614 app has passed.
07/06/2026
- 08:43 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Thank you, Alex.
I will fix the test case, then retest etf, hopefully it will be enough. - 08:41 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur, I committed to testcases/1847 plenty of tests in @tests/persistence/flushing_validation/flush_pipeline_regress...
- 08:40 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Teodor Gorghe wrote:
> * *[MAJOR]* _functional_ @Block@.@rollback@ / @SavepointManager@.@rollback@: Removing the @tx...
07/02/2026
- 04:51 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> I could setup ETF and test myself, please let me know.
You can start doing the ETF setup, ... - 04:49 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I think the first finding is relevant because if I run the tests manually, it passes. I think there is something rela...
- 04:47 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- If this is going to be substantial effort on your part, I could setup ETF and test myself, please let me know.
- 04:45 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I still have not found the procedure because the test suite is large.
Please check the automated code review and s... - 03:14 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Teodor,
Please send me in private the 4gl sources for the failing test.
07/01/2026
- 03:13 PM Bug #11573: Remove unnecessary JDBC savepoint during validation
- There are some tests from ETF which has failed and these are unexpected.
Check @devsrv01:/tmp/tg.20260701/11573.zip@ - 08:12 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Chui regression tests passed, the only one left is ETF, which is tested by Teodor.
- 01:56 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> Not, just the ones I mentioned. Should I continue with those?
Yes, please. - 01:56 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Not, just the ones I mentioned. Should I continue with those?
- 01:54 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> Artur Școlnic wrote:
> > Another customer application: smoke tests will be done by Razvan to... - 01:53 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur Școlnic wrote:
> Another customer application: smoke tests will be done by Razvan tomorrow morning.
This on... - 09:15 AM Bug #11588: Implement a dedicated Query implementation for CAN-FIND
- The reason for me not to be that optimistic is that we did a good job previously 🤠, based on the existing constraints...
- 08:44 AM Bug #11588: Implement a dedicated Query implementation for CAN-FIND
- > There is no actual hydration of the record (as noted above, an empty (all fields nulls) is created if the record is...
- 08:33 AM Bug #11588: Implement a dedicated Query implementation for CAN-FIND
- To have a base to start from, I will describe current state.
For stand-alone function, there are two kind of it: u... - 08:19 AM Bug #11588: Implement a dedicated Query implementation for CAN-FIND
- From a conversion perspective, I would greatly prefer if we implement this similar to how we implement functions (e.g...
- 07:28 AM Bug #11588: Implement a dedicated Query implementation for CAN-FIND
- The goal is to achiave a different query implementation for CAN-FIND construct instead of leveraging the @FindQuery@ ...
- 07:19 AM Bug #11588 (New): Implement a dedicated Query implementation for CAN-FIND
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... - 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 ... - 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... - 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 ... - 07:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- I used an inner procedure. Will test with an external one.
- 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... - 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... - 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... - 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 ... - 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... - 06:10 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Sorry, that was supposed to be a question :)
Should i address those findings? - 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. - 06:06 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Artur, some AI observations:
* *[MAJOR]* _functional_ @Validation@.@flush@: @dmlSavepoint.complete()@ runs after t... - 05:50 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Can I continue testing?
- 05:40 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- start.p...
- 04:40 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- No, I will come up with one.
- 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?
- 04:38 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Changed priority to reflect the urgency of the fix.
- 03:42 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Thank you, Ovidiu.
I will start testing while Constantin looks over the changes.
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... - 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... - 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 ...
- 02:16 AM Bug #11573: Remove unnecessary JDBC savepoint during validation
- Ovidiu, please take a look again at rev 16623.
- 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... - 09:30 AM Bug #11576 (Review): Fix outer-join iteration handling for nullOuter.
- ...
Also available in: Atom