Project

General

Profile

Activity

From 08/11/2024 to 09/09/2024

09/10/2024

08:10 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
First, the good news.
It seems that a tenant change cannot be performed while in a database transaction. In case thi...
Ovidiu Maxiniuc

09/09/2024

05:30 PM Bug #9133: Array subscript is out of range stops the evaluation of other expressions in the where...
This is actually happening in the case of one of our customer, so it needs to be fixed. See #7143-1204.
The (anony...
Ovidiu Maxiniuc

09/06/2024

07:13 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Short update on task status:
* I managed to get a stable revision of 9036a after the rebase. Committed revision 1543...
Ovidiu Maxiniuc

09/05/2024

07:20 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
> When writing 4GL code and the tenant is changed, this MUST happen outside any transaction. All buffers must be flus... Greg Shah
08:03 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
I fixed locking in tenant mode. The fields of @Tenant@ container which must be final are wrapped in a new class which... Ovidiu Maxiniuc
05:06 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> The second issue is that the SysError @tt already exists@ is not caught in a catch block, the...
Artur Școlnic

09/04/2024

04:50 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Go ahead and move fields from @Context@ to @Tenant@ as needed. Keep in mind that all fields in @Tenant@ must be immut... Eric Faulhaber
02:46 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
As part of my tests of the 9036a/15426 I used two concurrent users which execute basic CRUD operations on the databas... Ovidiu Maxiniuc
01:50 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
The changes in 9036a/15426 look good to me. What is left to implement for this task to be complete (not considering #... Eric Faulhaber
03:33 AM Bug #9133: Array subscript is out of range stops the evaluation of other expressions in the where...
... Lorian Sandu
03:32 AM Bug #9133 (Internal Test): Array subscript is out of range stops the evaluation of other expressi...
Lorian Sandu

09/03/2024

07:44 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
No, you are right. That was just my brain being lazy.
I addressed the issue. Also, I fixed a problem with re-initial...
Ovidiu Maxiniuc
05:53 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Ovidiu Maxiniuc wrote:
> Actually, I used the database name, in lowercase. That was also to make sure there are no c...
Eric Faulhaber
10:15 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Eric Faulhaber wrote:
> Greg Shah wrote:
> > [...] The table-level annotation can help us with our implementation o...
Greg Shah
09:58 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Actually, I used the database name, in lowercase. That was also to make sure there are no conflicts with the default ... Ovidiu Maxiniuc
07:54 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Ovidiu Maxiniuc wrote:
> > The default tenant's @Tenant@ object would be created when the @Persistence@ object is in...
Eric Faulhaber
08:54 AM Bug #9127: Decimal values with precision over 50 can't be inserted in the persistent databases.
Values like @4000000000000000000000000000000000000000000000@, with more than 40 digits, can be stored in OE persisten... Artur Școlnic
08:48 AM Bug #9127 (New): Decimal values with precision over 50 can't be inserted in the persistent databa...
Artur Școlnic
07:22 AM Feature #5219: implement native full-text search for word index and CONTAINS support
> The exploration and possible use of database native support to implement CONTAINS support is considered part of thi... Greg Shah

09/02/2024

05:16 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Eric Faulhaber wrote:
> Ovidiu Maxiniuc wrote:
> > But why do you mean by breaking the encapsulation? Pinning the @...
Ovidiu Maxiniuc
03:56 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Greg Shah wrote:
> [...] The table-level annotation can help us with our implementation of shared vs multi-tenant ta...
Eric Faulhaber
07:41 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
> 2. Switching to multi-tenant database mode requires reconversion
Please note that an important objective of our ...
Greg Shah

08/30/2024

06:06 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Ovidiu Maxiniuc wrote:
> But why do you mean by breaking the encapsulation? Pinning the @Persistence@ object to a sp...
Eric Faulhaber
02:40 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Eric Faulhaber wrote:
> I've also been thinking more about the "need to reconvert for multi-tenancy mode" aspect we ...
Ovidiu Maxiniuc
02:27 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Eric Faulhaber wrote:
> We discussed this, but I don't think it is a settled point yet. If we revert the changes you...
Ovidiu Maxiniuc
01:44 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
I've also been thinking more about the "need to reconvert for multi-tenancy mode" aspect we discussed. We noted that ... Eric Faulhaber
01:27 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Ovidiu Maxiniuc wrote:
>
> *1. A @Persistence@ object for a logical database is not enough*
>
> My commits in 9...
Eric Faulhaber
11:58 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
The investigations for _meta database lead me to other issues. We discussed today and here is a summary of our meet.
...
Ovidiu Maxiniuc
09:06 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
To summarize, there are 2 issues. The first one is that @no-error@ is not honored in FWD when a handle is deleted and... Artur Școlnic

08/29/2024

09:40 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Replacing @ErrorManager.recordOrThrowError@ with @ErrorManager.recordOrShowDatabaseError@ did not solve the issue. Artur Școlnic
08:28 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
For errors conditions being raised when database is accessed, we found quirks which we solved via calling @ErrorManag... Constantin Asofiei
08:02 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
... Artur Școlnic
07:59 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
... Artur Școlnic
06:18 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
start.p... Artur Școlnic
05:02 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> Coming back to #9091-37, it looks like proc2 should not be executed at all, but it is execute...
Artur Școlnic
04:50 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Coming back to #9091-37, it looks like proc2 should not be executed at all, but it is executed in FWD, which causes t... Artur Școlnic
03:32 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
In @ProcedureManager.delete()@... Artur Școlnic
02:54 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
start.p... Artur Școlnic
07:11 AM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
> But the information is pretty much similar (like @_File@ and related tables).
These databases share the same ex...
Greg Shah

08/28/2024

06:42 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
Earlier today I committed my latest changes to 9036a and rebased the branch to latest trunk. The current revision is ... Ovidiu Maxiniuc
08:28 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> ... and used @run checkNew.@ in @proc1@ and in the @finally@ block of @start.p@. In bot...
Constantin Asofiei
07:51 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
As far as I know, errors like @tt already exists@ are not supposed to be caught with @catch e as Progress.Lang.Error@... Artur Școlnic
07:38 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
In FWD, tt is flushed 3 times, at the create, on the associate of the dataset (throws the error) and when exiting the... Artur Școlnic
07:23 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Adding @release tt@ in proc1 after the creates causes the error not to be caught in 4gl, this matches the behavior in... Artur Școlnic
06:53 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
I've added this in @parser.p@:... Constantin Asofiei
06:50 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Could running of a procedure with an output parameter cause a flush and expose the errors in the procedures ran previ... Artur Școlnic
06:49 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> Another test: use a secondary buffer @def buffer buftt1 for tt1.@ in @proc1@ instead of ...
Artur Școlnic
06:45 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> OK, now test in OpenEdge with a @TABLE@ parameter instead of @DATASET@, add a @proc3@ wi...
Artur Școlnic
06:43 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Another test: use a secondary buffer @def buffer buftt1 for tt1.@ in @proc1@ instead of the implicit buffer, and test... Constantin Asofiei
06:42 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
OK, now test in OpenEdge with a @TABLE@ parameter instead of @DATASET@, add a @proc3@ with a @def output parameter ta... Constantin Asofiei
06:42 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
proc2 does not seem to be executed, however, if the output parameter is not used, the error is no longer thrown at al... Artur Școlnic
06:34 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
... Artur Școlnic
06:18 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Add a @MESSAGE@ statement in proc2, so we know if that proc2 body is executed or not. Also, test this with and witho... Constantin Asofiei
06:00 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
start.p... Artur Școlnic
05:52 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> No, the output of @ex:getMessage(1)@.
@tt already exists...@
Artur Școlnic
05:45 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> Constantin Asofiei wrote:
> > Who exactly throws this error - @reader:sax-parse()@ or @run p...
Constantin Asofiei
05:44 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> Constantin Asofiei wrote:
> > What is the error message being caught in OpenEdge?
> Caught...
Constantin Asofiei
05:43 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> Who exactly throws this error - @reader:sax-parse()@ or @run proc2@?
@run proc2@
Artur Școlnic
05:42 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Constantin Asofiei wrote:
> What is the error message being caught in OpenEdge?
Caught exception!
Artur Școlnic
05:42 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
What is the error message being caught in OpenEdge? Who exactly throws this error - @reader:sax-parse()@ or @run proc... Constantin Asofiei
05:31 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
The parser is a program designed to parse an XML file and insert the data in the temp tables defined in it. The error... Artur Școlnic
05:17 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
start.p... Artur Școlnic
05:15 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
It seems like the external procedure is deleted at the end of the main program and all of it's resources are closed, ... Artur Școlnic

08/26/2024

08:49 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
I've added MESSAGE statements like this:
* main.p...
Constantin Asofiei
04:39 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
In @ProcedureManager@, for @External.execute()@, there are 3 finalizables objects added to the @finalizables@ set, on... Artur Școlnic
08:08 AM Feature #7960 (Test): Allow query logs to be collected in a H2 database
Ioana-Cristina Prioteasa
08:08 AM Feature #7960: Allow query logs to be collected in a H2 database
Branch 7960a merged to *trunk as rev. 15394* and archived. Ioana-Cristina Prioteasa
06:36 AM Feature #7960 (Merge Pending): Allow query logs to be collected in a H2 database
I am OK with the changes. Please go ahead and merge 7960a to trunk. Alexandru Lungu

08/24/2024

09:03 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
9036a branch was updated. Latest revision is 15388.
Changes:
* Improve database awareness of tenant information;
...
Ovidiu Maxiniuc

08/23/2024

08:52 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> Considering that the proc1 is an internalProcedure, is persistent and the @staticResources@ i...
Constantin Asofiei
08:48 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Considering that the proc1 is an internalProcedure, is persistent and the @staticResources@ is empty, could someone s... Artur Școlnic
07:58 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
In @scopeFinished@ for the proc1, the procedure gets deleted only if it is external and not persistent,
which in th...
Artur Școlnic
07:18 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
On @popScope@ of the buffer, @finishedImpl@ is not executed, instead the @worldScope@ attribute is set to true. Artur Școlnic
04:32 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
@target.finished()@ for a @BufferManager@ does... Artur Școlnic
03:54 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
The buffer is in @PersistentProcScope@, but the problem is still persisting, @target.finished()@ is called to soon or... Artur Școlnic
03:27 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
The opening of the scope in the external procedure is correct. To propagate it, FWD is checking if the procedure was ... Alexandru Lungu
03:19 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
When using @run proc1 in external@, the conversion for @external.p@ is ... Artur Școlnic

08/22/2024

06:34 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
9036a branch was updated. Latest revision is 15387.
Changes:
* Made @Database@ objects tenant-friendly;
* Started ...
Ovidiu Maxiniuc
02:17 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
To summary (hopefully most or all of) our discussion today...
*@Database@ Object Use*
We agreed that we want to...
Eric Faulhaber
01:30 PM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
> I did not see that attribute in the @.df@ file I have. The table @test@ is defined as:[...]
I think that attribu...
Greg Shah
01:05 PM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
Radu,
I did not see that attribute in the @.df@ file I have. The table @test@ is defined as:...
Ovidiu Maxiniuc
12:02 PM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
Radu got to the schema answer before I could post. :)
> I do not think the tables from different tenants can be in...
Greg Shah
11:48 AM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
Ovidiu Maxiniuc wrote:
> But in order to generate that, the information must come from somewhere. How is this inform...
Radu Apetrii
11:32 AM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
Yep, I forgot about the DMO annotations.
But in order to generate that, the information must come from somewhere. H...
Ovidiu Maxiniuc
10:37 AM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
I don't think this is correct.
The default database and the tenant databases have the same exact schema. There is...
Greg Shah
08:45 AM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
If I understand it correctly, when a database is declared (generically speaking) we get the following information:
#...
Ovidiu Maxiniuc
07:33 AM Feature #9093: add protection for multi-tenant imports to optionally only import tables that are ...
When running import, the user should be able to optionally force the import to limit itself to one the following:
...
Greg Shah
07:28 AM Feature #9093 (Closed): add protection for multi-tenant imports to optionally only import tables ...
Greg Shah
09:28 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
In @TransactionManager.processFinalazables()@, the record buffer is missing from the @blk.finalizables@ when using @r... Artur Școlnic
09:16 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur Școlnic wrote:
> @run external.p@ is converted as an externalProcedure.
> [...] is converted as an internalPr...
Artur Școlnic
09:11 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
I meant that the @proc1@ is @internalProcedure@.... Artur Școlnic
09:09 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
I converted the example in #9091-11 and I get:... Alexandru Lungu
08:45 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
@run external.p@ is converted as an externalProcedure.... Artur Școlnic
08:27 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Alexandru Lungu wrote:
> Who is causing the release of @tt@ the second time? The first time it is clear.
I added ...
Artur Școlnic
08:16 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Who is causing the release of @tt@ the second time? The first time it is clear. Alexandru Lungu
08:10 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Releasing tt after the second create does cause the error to be thrown. Artur Școlnic
08:03 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
Artur, the first record that you created is flushed to the database because you re-use the buffer (causing an implici... Alexandru Lungu
07:57 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
@getUnvalidatedIndices@ returns null because the unique bit set is being checked against the Map of properties touche... Artur Școlnic
07:32 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
When using composite indices in this context, @getUnvalidatedIndices@ returns null instead of the bit set representin... Artur Școlnic
06:26 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
main.p... Artur Școlnic
06:18 AM Bug #9091 (WIP): Unique composite index is ignored when create is used in an external procedure
Artur Școlnic
06:18 AM Bug #9091: Unique composite index is ignored when create is used in an external procedure
This ticket is derived from #8912-216. Artur Școlnic
06:17 AM Bug #9091 (WIP): Unique composite index is ignored when create is used in an external procedure
Artur Școlnic
03:44 AM Feature #7960: Allow query logs to be collected in a H2 database
Committed on *7960a rev. 15355* formatting changes.
The testing plan has been successfully completed, please refer...
Ioana-Cristina Prioteasa

08/20/2024

02:26 PM Feature #7960: Allow query logs to be collected in a H2 database
Only small formatting issues:
* return javadoc doesn't need to have the type; only the description of the returned v...
Alexandru Lungu
08:42 AM Feature #7960 (Internal Test): Allow query logs to be collected in a H2 database
Eric Faulhaber
12:13 PM Bug #9078: emit FindQuery as (reused) variables
There is another point here. When a Java method gets called 10k's of times, then the local-var FIND will be created ... Constantin Asofiei
11:13 AM Bug #9078: emit FindQuery as (reused) variables
A @FIND@ statement can be executed 10k's or more just for simple API calls. This requires, for each execution:
* a ...
Constantin Asofiei
11:00 AM Bug #9078 (Review): emit FindQuery as (reused) variables
Constantin Asofiei

08/19/2024

05:45 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
> I think the best solution is a runtime flag (in @directory.xml@)
Whether or not a table is shared or multi-tena...
Greg Shah
05:04 PM Bug #9036 (WIP): Multi-tenancy: refactor the database in Persistence context-wise
Multiple issue reported in my previous note are caused because some objects are cached locally, in different persiste... Ovidiu Maxiniuc
08:26 AM Feature #7960: Allow query logs to be collected in a H2 database
Ioana-Cristina Prioteasa wrote:
> Made a small error in @CentralLoggerFile@ at @fileCount@ and @fileLimit@ condition...
Galya B
07:48 AM Feature #7960: Allow query logs to be collected in a H2 database
Made a small error in @CentralLoggerFile@ at @fileCount@ and @fileLimit@ conditions. Resolved it and committed the fi... Ioana-Cristina Prioteasa
05:47 AM Feature #7960: Allow query logs to be collected in a H2 database
Addressed code review.
I retested the scenario where @filepath@ is null or empty, as I was concerned about potentia...
Ioana-Cristina Prioteasa
03:47 AM Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
Greg Shah wrote:
> OE knows whether a table is shared (default tenant) or is multi-tenant. In OE, setting the tenan...
Radu Apetrii

08/18/2024

05:51 PM Bug #9036: Multi-tenancy: refactor the database in Persistence context-wise
I have created task branch 9036a and committed the changes to problems I encountered. Latest revision is 15386. Below... Ovidiu Maxiniuc

08/15/2024

07:32 AM Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
OE knows whether a table is shared (default tenant) or is multi-tenant. In OE, setting the tenant using @SET-DB-CLIE... Greg Shah
07:31 AM Feature #9057 (Test): enable intermixed access to default tenant (shared) data and tenant-specifi...
Greg Shah

08/14/2024

03:39 AM Bug #9034: FindQuery unique fails in a self join context
Alexandru Lungu wrote:
> * I am a bit confused with the state of this branch. I already reviewed 9034a/15373 in #903...
Artur Școlnic
03:18 AM Bug #9034: FindQuery unique fails in a self join context
Review of 9034a:
* I am a bit confused with the state of this branch. I already reviewed 9034a/15373 in #9034-9. May...
Alexandru Lungu
02:11 AM Feature #7960: Allow query logs to be collected in a H2 database
Ioana-Cristina Prioteasa wrote:
> Committed changes to *7960a rev.15352*. Added a concrete version of @CentralLogger...
Galya B

08/13/2024

11:17 AM Bug #9034: FindQuery unique fails in a self join context
Alexandru, please review. Eric Faulhaber
05:57 AM Bug #9034 (Review): FindQuery unique fails in a self join context
I committed 9034a/15373 and 9034a_h2/51, added support for identifying ambiguous unique find. Artur Școlnic
09:32 AM Feature #7960: Allow query logs to be collected in a H2 database
Committed changes to *7960a rev.15352*. Added a concrete version of @CentralLogger@ that allows dynamic file path con... Ioana-Cristina Prioteasa
06:55 AM Feature #7960: Allow query logs to be collected in a H2 database
The existing code was using the @CentralLogger@ format and @WARNING@ log level, so I think it's would be great if the... Ioana-Cristina Prioteasa
05:24 AM Feature #7960: Allow query logs to be collected in a H2 database
Ioana-Cristina Prioteasa wrote:
> I could add a server hook and if profiling was enable to close the file.
I think ...
Galya B
04:27 AM Feature #7960: Allow query logs to be collected in a H2 database
I looked into the file closing issue. The problem is here:
In @P2JQueryStatisticsConfiguration@:...
Ioana-Cristina Prioteasa
08:57 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
Branch 8593e was merged to trunk rev 15379 and archived. Constantin Asofiei
08:31 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
Greg Shah wrote:
> If this is ready to merge, it can go after 8233a. Constantin/Alexandru make the call.
Queued fo...
Constantin Asofiei
08:16 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
If this is ready to merge, it can go after 8233a. Constantin/Alexandru make the call. Greg Shah
08:09 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
I agree, I reckon 7156c fails because a @StopConditionException@. The SQL is wrong as a column is not found.
*So*, I...
Alexandru Lungu
08:06 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
This passed ETF and also solves #9048. We need to merge it, even if it does not address issues in 7156c. Constantin Asofiei
03:19 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
> Alexandru, I've backed out the 'cleanup' change in RecordBuffer.finishedImpl; I don't have a recreate yet, but I'll... Alexandru Lungu
08:43 PM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
Review of 8593e/15379 (I assume this is your 15354 after the rebase).
I think the code is OK. I like the direct ac...
Ovidiu Maxiniuc

08/12/2024

11:21 AM Bug #8593: H2 performance improvement for table 'truncate by multiplex'
Ovidiu, please see 8593e 15354 - this fixes better ACCEPT-CHANGES.
Alexandru, I've backed out the 'cleanup' change...
Constantin Asofiei
07:12 AM Feature #7960: Allow query logs to be collected in a H2 database
h3. Test results
Tested with a small testcase in dataset. Below is an example output.
!7960a_results.png!
Ad...
Ioana-Cristina Prioteasa
 

Also available in: Atom