Activity
From 05/23/2025 to 06/21/2025
06/21/2025
- 06:45 PM Feature #7504: Export data tool from FWD into .d files
- I cannot update to those revisions. The latest I see on branch 7504b is 15914. Maybe you forgot to bind / push?
- 07:54 AM Feature #7504: Export data tool from FWD into .d files
- After exporting data from different customer databases, i've rebase to latest trunk and made two commits to @7504b@ :...
06/20/2025
- 04:28 PM Bug #9078: emit FindQuery as (reused) variables
- I was thinking about @fqueryArray[0] = new FindQuery();@ initialization. To have a more compact code, we could emit i...
- 07:39 AM Bug #9078: emit FindQuery as (reused) variables
- > will the template above do to generate FindQuery[] fqueryArray = new FindQuery[5]; or is there a way to make it sim...
- 05:45 AM Bug #9078: emit FindQuery as (reused) variables
- The solution would be to move @fqueryArray[0] = new FindQuery();@ in the @body()@, emit the FindQuery normally withou...
- 05:37 AM Bug #9078: emit FindQuery as (reused) variables
- The following test:...
- 10:46 AM Feature #10169: result-set streaming (and asynchronous programming?)
- The java test cases show that the benefit of running the query in a separate thread is similar with running the busin...
- 08:02 AM Feature #10169: result-set streaming (and asynchronous programming?)
- Well, this changes things. If the for each body cannot be executed in a new thread, I will go the other way and try t...
- 07:57 AM Feature #10169: result-set streaming (and asynchronous programming?)
- I don't think we should look at pushing 4GL logic into other threads. Our core design will not allow this without a ...
- 07:46 AM Feature #10169: result-set streaming (and asynchronous programming?)
- Artur Școlnic wrote:
> I attached the source for this test.
- 07:44 AM Feature #10169: result-set streaming (and asynchronous programming?)
- Artur Școlnic wrote:
> I started working on introducing async in @forEachWorker@, currently there are issues with ou... - 07:35 AM Feature #10169: result-set streaming (and asynchronous programming?)
On another note, I found a way to introduce artificial latency on a network adapter.
The delay is per tcp packet, ...- 07:32 AM Feature #10169: result-set streaming (and asynchronous programming?)
- I believe another way to utilize the result set streaming and async programming is streaming results in a for each wh...
- 06:38 AM Feature #9455: port native user defined functions to SQL Server
- At the time I wrote @CREATE FUNCTION dbo.modulo_ii (@p1 INT, @p2 INT) RETURNS BIGINT AS@ I was not able to test it. A...
- 05:44 AM Feature #9455: port native user defined functions to SQL Server
- Constantin Asofiei wrote:
> What if you call a PROCEDURE from a FUNCTION?
This could be done. And error is raised. - 05:21 AM Feature #9455: port native user defined functions to SQL Server
- What if you call a PROCEDURE from a FUNCTION?
- 05:21 AM Feature #9455: port native user defined functions to SQL Server
- I see that in T-SQL, statements like @RAISERROR('Dates before October 15, 1582 are not yet supported', 16, 1);@. coul...
- 03:52 AM Bug #10181: Date shifted one day earlier when importing data
- Thanks, Ovidiu.
What testing should be performed for this change?
06/19/2025
- 10:24 AM Bug #10181 (Internal Test): Date shifted one day earlier when importing data
- I am OK with the change because the UTC will leave the data unaffected by the TZ.
However, I think all occurrences... - 08:30 AM Bug #10181 (Review): Date shifted one day earlier when importing data
- 08:30 AM Bug #10181 (WIP): Date shifted one day earlier when importing data
- 08:26 AM Bug #10181: Date shifted one day earlier when importing data
- In #7504-31 :
> I also encountered a potential bug during *import*:
> * I imported a .d file containing the value... - 08:05 AM Bug #10181 (Test): Date shifted one day earlier when importing data
- 08:25 AM Feature #7504: Export data tool from FWD into .d files
- When testing the export tool and importing/exporting the db from a large gui app i encountered again this type of err...
- 07:33 AM Bug #9078: emit FindQuery as (reused) variables
- The following template worked:...
- 07:20 AM Bug #9078: emit FindQuery as (reused) variables
- I've adjusted the template in the following way:...
- 07:06 AM Bug #9078: emit FindQuery as (reused) variables
- I found the @named_array@ template in @java_templates.tpl@ and managed to generate something like:...
- 06:07 AM Feature #10169: result-set streaming (and asynchronous programming?)
- I think this implies tracking and storing the time of execution for queries and iterative blocks that have queries (a...
- 05:44 AM Feature #10169: result-set streaming (and asynchronous programming?)
- One approach for implementation would be to measure conditions at runtime and shift into this streaming/async mode wh...
- 04:59 AM Feature #10169 (WIP): result-set streaming (and asynchronous programming?)
- Below you can find the result of testing async execution for db queries combined with result set streaming.
To simul...
06/18/2025
- 04:14 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- Eric Faulhaber wrote:
> @ImportWorker$TenantIdContext.prepareNextBracket@: Why is it safe to fall back to using the ... - 02:22 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- One other thing I noticed in my last review, though it already existed in the code before your recent changes. In @Im...
- 02:14 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- Code review 10094a/15985-15988:
@ImportWorker$TenantIdContext.prepareNextBracket@: Why is it safe to fall back to ... - 07:56 AM Bug #10171: Word Index/CONTAINS support for MS SQL Server.
- Another version without using the @dbo.Delimiters@ table:
{{Collapse(See sql ...)... - 05:10 AM Bug #10171: Word Index/CONTAINS support for MS SQL Server.
- This task is for implementing support for word indexing and CONTAINS statements in Microsoft SQL Server.
As part of ... - 04:14 AM Bug #10171 (Test): Word Index/CONTAINS support for MS SQL Server.
- 07:06 AM Feature #9456: implement SQL Server dialect and helpers
- > * I hit another MSSQL implementation restriction, one we were not aware of in the iteration of several years ago: t...
- 06:56 AM Feature #9456: implement SQL Server dialect and helpers
- Related to my note #9456-8: with my current changes in 9456a, I encountered in @hotel_runtime@ a query where predicat...
- 08:12 PM Feature #9456: implement SQL Server dialect and helpers
- The @ORDER BY@ issue was partially resolved. In case of @UNIQUE@ finds, the HQL bundle was expressly setting the sort...
- 11:32 PM Feature #7020: always use "expanded" extent fields
- Eric Faulhaber wrote:
> Stefanel, did we ever get these ChUI test results? Is there any other testing needed?
Unf...
06/17/2025
- 04:01 PM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> Radu tested @7020d@ with @<parameter name="expand-extents" value="false" />@ in @p2j.cfg... - 12:25 PM Feature #10169: result-set streaming (and asynchronous programming?)
- This seems quite promising, I especially like the idea of adding threading in to keep the data transfer happening in ...
- 12:23 PM Feature #10169: result-set streaming (and asynchronous programming?)
- From Artur in #9802-210:
As already discussed, one of the main reasons for the differences in performance we see i... - 12:20 PM Feature #10169 (WIP): result-set streaming (and asynchronous programming?)
- 08:00 AM Feature #9456: implement SQL Server dialect and helpers
- One more thing, related to paging. We knew that MSSQL does not have a @LIMIT@ / @OFFSET@ syntax for query pagination,...
- 05:22 AM Bug #10080: Temp-table records are leaking in can-find statements
- Sure.
- 05:21 AM Bug #10080: Temp-table records are leaking in can-find statements
- Eduard, 8308f wasn't backed out from 7156c/e. Please commit the necessary changes from 10080a to 7156c and 7156e.
- 05:18 AM Bug #10080 (Test): Temp-table records are leaking in can-find statements
- 10080a was merged to trunk rev 15986 and archived.
- 04:38 AM Bug #10080 (Merge Pending): Temp-table records are leaking in can-find statements
- Go ahead and merge now.
- 04:32 AM Bug #10080: Temp-table records are leaking in can-find statements
- Eduard Soltan wrote:
> Still haven't got an response from harness/web/report of an application testing.
Testing... - 03:49 AM Bug #10080: Temp-table records are leaking in can-find statements
- unit tests and smoke tests of a large gui application ✅
- chui regression tests ✅
- smoke tests of a gui appl...- 03:45 AM Bug #10080: Temp-table records are leaking in can-find statements
- Can this be queued for merge?
06/16/2025
- 04:58 AM Feature #9456: implement SQL Server dialect and helpers
- A 'new' old issue: the MSSQL and lack of support for boolean literals. That is the reason the @Dialect.supportsBoolea...
- 02:40 AM Bug #10080: Temp-table records are leaking in can-find statements
- Yes, they are passing and received the news from Danut that ETF has passed.
- 02:39 AM Bug #10080: Temp-table records are leaking in can-find statements
- Eduard Soltan wrote:
> Tested performed:
>
> - unit tests of a large gui application ✅
> - chui regression tests...
06/13/2025
- 05:56 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- I upgraded the project of the single customer to be MT-enabled. Committed to r89.
Here are the changes in @build.pro... - 04:13 PM Bug #6767: Possible name clashes in DMO classes
- I’m struggling to get the conversion to work as intended. For example, I’d like the @NEXT-SIBLING@ attribute converte...
- 02:20 PM Bug #6767: Possible name clashes in DMO classes
- Vladimir Tsichevski wrote:
> We should distinguish these cases within the conversion rules, perhaps using conditiona... - 02:13 PM Bug #6767: Possible name clashes in DMO classes
- Constantin Asofiei wrote:
> Vladimir Tsichevski wrote:
> > We need to update the conversion rules, as the correct m... - 01:40 PM Bug #6767: Possible name clashes in DMO classes
- Vladimir Tsichevski wrote:
> We need to update the conversion rules, as the correct method names are now @privateDat... - 09:52 AM Bug #6767: Possible name clashes in DMO classes
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
>
> > Looks like you don't need to revert.
> Good, now I ...
06/12/2025
- 12:11 PM Bug #6767: Possible name clashes in DMO classes
- Constantin Asofiei wrote:
> Looks like you don't need to revert.
Good, now I am running a customer big applicatio... - 12:02 PM Bug #6767: Possible name clashes in DMO classes
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
> > Review of 6767c rev 15980.
> > * @AbstractTempTable@
>... - 07:24 AM Bug #6767: Possible name clashes in DMO classes
- Constantin Asofiei wrote:
> Review of 6767c rev 15980.
> * @AbstractTempTable@
> ** line 2938 - please add back @d... - 05:05 AM Bug #6767: Possible name clashes in DMO classes
- Review of 6767c rev 15980.
* @AbstractTempTable@
** line 2938 - please add back @defBuffer.bufferManager@ instead o... - 10:22 AM Bug #9078: emit FindQuery as (reused) variables
- Danut, just keep in mind that a Map has a higher overhead than a plain array. That is why I am suggesting creating an...
- 02:24 AM Bug #9078: emit FindQuery as (reused) variables
- Alexandru Lungu wrote:
> Dănuț Filimon wrote:
> > I did not take into account that there might be a limitation to t...
06/11/2025
- 05:28 PM Bug #6767: Possible name clashes in DMO classes
- Eric Faulhaber wrote:
> Vladimir, this is a large set of changes. What testing do you propose?
I think, convert... - 05:22 PM Bug #6767 (Review): Possible name clashes in DMO classes
- Committed as 6767c rev. 15980. Please, review.
- 12:13 PM Bug #6767: Possible name clashes in DMO classes
- For @HandleChain@ and its ancestors I found 8 matching methods:...
- 11:43 AM Bug #6767: Possible name clashes in DMO classes
- Eric, Constantin,
I need you to confirm this:
*DMO setters* do not use *Java built-in types*. For example, we can... - 04:28 PM Feature #10142: allow UDFs to live in the public schema instead a UDF-specific schema
- A customer using PostgreSQL in the cloud requested that the native SQL UDFs representing Progress built-in functions ...
- 04:16 PM Feature #10142 (New): allow UDFs to live in the public schema instead a UDF-specific schema
- 10:39 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> I did not take into account that there might be a limitation to the number of local variables... - 09:14 AM Bug #9078: emit FindQuery as (reused) variables
- I did not take into account that there might be a limitation to the number of local variables that can be defined in ...
- 08:36 AM Bug #9078: emit FindQuery as (reused) variables
- I discussed with Artur and took time to take a look at all find queries from the problematic class. I took each one a...
- 07:59 AM Feature #7504 (Internal Test): Export data tool from FWD into .d files
- 07:50 AM Feature #7020: always use "expanded" extent fields
- Constantin Asofiei wrote:
> Is @expand-extents=true@ now the default and we need to configure projects which can't u... - 07:47 AM Feature #7020: always use "expanded" extent fields
- Is @expand-extents=true@ now the default and we need to configure projects which can't use this mode explicitly in p2...
- 07:17 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- I made sure the tables are not skipped if the @.d@ files are empty. Replacing all @System.out@ with proper logging.
... - 08:07 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- Greg Shah wrote:
> We will need to have tested that as well to confirm that it resolves everything safely.
As a fir...
06/10/2025
- 03:07 PM Bug #6767: Possible name clashes in DMO classes
- > And this refactor can be done automatically (with CTRL+SHIFT+G) in Eclipse, although each one needs to be done 'by ...
- 02:14 PM Bug #6767 (WIP): Possible name clashes in DMO classes
- 02:13 PM Bug #6767: Possible name clashes in DMO classes
- Constantin Asofiei wrote:
> Vladimir, did you use some script to 'sed' the changes?
No. I used Java reflection to c... - 01:17 PM Bug #6767: Possible name clashes in DMO classes
- Vladimir, did you use some script to 'sed' the changes? As Eric mentioned, there are lots of unintended changes. The...
- 12:59 PM Bug #6767: Possible name clashes in DMO classes
- Code review 6767b/15628-15629 (apologies for the long delay):
Overall, the changes look good, though I think we ar... - 09:08 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- The ideal test 10094a would be to have a logical database with the shared db at least two tenant dbs. The customer di...
- 08:50 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- > Please let me know if I got your question right.
Yes, mostly.
If the schema can be incorrect from prior runs ... - 08:24 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- What 10094a adds is that the empty tables from the (re-)imported database are guaranteed to be indexed.
Do you thi... - 05:53 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- I'm trying to determine if we need to write a migration script to cleanup existing MT installations so that they matc...
- 09:02 AM Bug #10111 (WIP): All statements are logged to a single text file for P2JQueryLogger and SQLState...
- Addressed the 1st and 2nd point in @10111a/15979@.
For the 3rd, I am thinking of creating a super class for those 2 ... - 07:57 AM Bug #10111: All statements are logged to a single text file for P2JQueryLogger and SQLStatementLo...
- +Review of 10111a/15978.+
The changes are logical. The reason is explained in 1st note above. Good catch!
The c... - 06:34 AM Bug #10111 (Review): All statements are logged to a single text file for P2JQueryLogger and SQLSt...
- Committed @10111a/15978@. The changes are quite simple: just removing the static keyword for @fileLogger@ in @SQLStat...
- 06:33 AM Bug #10111 (WIP): All statements are logged to a single text file for P2JQueryLogger and SQLState...
- 06:02 AM Bug #10111: All statements are logged to a single text file for P2JQueryLogger and SQLStatementLo...
- While using @SQLStatementLogger@ for multiple databases, I discovered that all the statements are logged to a single ...
- 04:58 AM Bug #10111 (Test): All statements are logged to a single text file for P2JQueryLogger and SQLStat...
- 06:39 AM Bug #9078: emit FindQuery as (reused) variables
- Artur ran a conversion for a customer application and found a conversion issue. I plan to work with Artur to identify...
- 05:55 AM Bug #9994 (Rejected): Err: Cannot run GET methods on query until it is opened.
- 01:56 AM Bug #9994: Err: Cannot run GET methods on query until it is opened.
- This can be closed/rejected.
- 03:14 AM Feature #9440 (Test): get-codepage() function should work with CLOB fields
- Branch 9440a was merged to trunk rev 15975 and archived.
- 02:49 AM Feature #9440 (Merge Pending): get-codepage() function should work with CLOB fields
- Please rebase and merge 9440a now.
- 12:18 AM Bug #10080: Temp-table records are leaking in can-find statements
- Updated @query/canfindmultiplex@ testcases.
06/09/2025
- 07:37 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- I am not sure I fully understand the question.
TL;DR: If the import decides that a table is processed, the indexes... - 08:03 AM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- Does this mean that existing imported databases may have some indexes which need to be dropped?
06/06/2025
- 06:55 PM Feature #10094: RECIDs from different tenants of same logical database should not overlap
- As discussed with Constantin, I did a bit of reworking on the import to be sure the indexes of the tables are correct...
- 08:14 PM Feature #10094 (Review): RECIDs from different tenants of same logical database should not overlap
- I have created branch 10094a and committed the changes as revision 15970.
The implementation was actually easier t... - 11:18 AM Bug #10083: Infinite loop when changing walking index fields
- CHUI Regression tests passed with 10083a. ☑️
Large GUI Application unit tests passed. ☑️ - 07:11 AM Bug #10083 (Internal Test): Infinite loop when changing walking index fields
- Tomasz Domin wrote:
> Do you mean @10083a/15961@ as I can confirm that, results are fine with @10083a/15961@.
> Why... - 06:41 AM Bug #10083: Infinite loop when changing walking index fields
- Eduard Soltan wrote:
> Tomasz Domin wrote:
> > Eduard Soltan wrote:
> > > Tomasz, could you run it again with 1008... - 05:40 AM Bug #10083: Infinite loop when changing walking index fields
- Tomasz Domin wrote:
> Eduard Soltan wrote:
> > Tomasz, could you run it again with 10083-13 patch?
>
> The resul... - 02:46 AM Bug #10083: Infinite loop when changing walking index fields
- Eduard Soltan wrote:
> Tomasz, could you run it again with 10083-13 patch?
The result stays the same:... - 02:34 AM Bug #10083: Infinite loop when changing walking index fields
- Eduard Soltan wrote:
> Tomasz, could you run it again with 10083-13 patch?
I am working on this. Is this patch fo... - 02:23 AM Bug #10083: Infinite loop when changing walking index fields
- Tomasz, could you run it again with 10083-13 patch?
- 10:55 AM Support #10101: broader testing of various database performance configuration options
- Different database implementations offer various performance tuning configuration settings. For example, PostgreSQL o...
- 02:08 AM Bug #10104: Analyze performance drop after rev. 15963
- This task aims to analyze the performance drop of trunk rev 15963.
In one of our testing, a performance decrease of... - 01:58 AM Bug #10104 (New): Analyze performance drop after rev. 15963
06/05/2025
- 03:51 PM Support #10101 (New): broader testing of various database performance configuration options
- 02:09 PM Bug #10080: Temp-table records are leaking in can-find statements
- Tested performed:
- unit tests of a large gui application ✅
- chui regression tests ✅
Is any additional testin... - 02:00 AM Bug #10080: Temp-table records are leaking in can-find statements
- Constantin Asofiei wrote:
> Eduard, please see #10088-57 - is this task fixing the CAN-FIND sub-select, so that now ... - 01:51 AM Bug #10080: Temp-table records are leaking in can-find statements
- Eduard, please see #10088-57 - is this task fixing the CAN-FIND sub-select, so that now it correctly has the _multipl...
- 12:39 PM Bug #10083: Infinite loop when changing walking index fields
- Eduard Soltan wrote:
> Tomasz Domin wrote:
> > No wiki yet.
> > See #9270, #6860#80, @support/harness/readme.txt@ ... - 09:54 AM Bug #10083: Infinite loop when changing walking index fields
- ...
- 09:23 AM Bug #10083: Infinite loop when changing walking index fields
- Tomasz Domin wrote:
> I've run @support/harness/test/cross_session_test.xml@ dirty share tests and they fail much mo... - 09:12 AM Bug #10083: Infinite loop when changing walking index fields
- Tomasz Domin wrote:
> No wiki yet.
> See #9270, #6860#80, @support/harness/readme.txt@ (that will go into Wiki)
> ... - 05:53 AM Bug #10083: Infinite loop when changing walking index fields
- No wiki yet.
See #9270, #6860#80, @support/harness/readme.txt@ (that will go into Wiki)
Attached @zfile_set.txt@ fo... - 05:04 AM Bug #10083: Infinite loop when changing walking index fields
- Is there a wiki to run @support/harness/test/cross_session_test.xml@?. I tried to run them myself it was giving me al...
- 04:54 AM Bug #10083: Infinite loop when changing walking index fields
- I've run @support/harness/test/cross_session_test.xml@ dirty share tests and they fail much more compared to @trunk@....
- 12:12 PM Feature #7504: Export data tool from FWD into .d files
- Lorian Sandu wrote:
> *Roger*, when you are available, please have a look.
Updates look good. Again, the use case f... - 12:08 PM Feature #7504: Export data tool from FWD into .d files
- Greg Shah wrote:
> Roger: I would prefer if @import.sh@ *did not* work on multiple database at once. The reasoning:... - 10:00 AM Feature #7504: Export data tool from FWD into .d files
- Roger: I would prefer if @import.sh@ *did not* work on multiple database at once. The reasoning: separate logs for e...
- 06:58 AM Feature #7504: Export data tool from FWD into .d files
- Committed to @7504b / rev 15912@ :
@export.sh@:
* added support for multiple databases export
* added support fo... - 04:01 AM Feature #7504: Export data tool from FWD into .d files
- Roger Borrello wrote:
> I'm also curious why you don't allow a list of DBs to be passed in, same as @import.sh@? I'm... - 09:15 AM Bug #9078: emit FindQuery as (reused) variables
- Rebased *9078b* to latest *trunk/15969*, the branch is now at revision *15973*.
- 03:20 AM Feature #9440: get-codepage() function should work with CLOB fields
- Teodor Gorghe wrote:
> Ok, thanks.
> Related to this task, I noticed that the task status become "Internal Test".
...
06/04/2025
- 02:19 PM Feature #7504: Export data tool from FWD into .d files
- > I don't think adding as a reviewer adds as a watcher... is that a function that can be added?
No - 11:07 AM Feature #7504: Export data tool from FWD into .d files
- I'm also curious why you don't allow a list of DBs to be passed in, same as @import.sh@? I'm not sure I understand th...
- 10:44 AM Feature #7504: Export data tool from FWD into .d files
- Lorian Sandu wrote:
> Greg Shah wrote:
> > Roger: Please review @export.sh@.
>
> Roger, the revisions that need ... - 08:56 AM Feature #7504: Export data tool from FWD into .d files
- Greg Shah wrote:
> Roger: Please review @export.sh@.
Sorry I missed this. I don't think adding as a reviewer adds... - 08:22 AM Feature #7504: Export data tool from FWD into .d files
- Attached the @build.properties@, @build.xml@ and @build_db.xml@ from @hotel@ with support for @export@.
After revi... - 10:01 AM Bug #10080 (Internal Test): Temp-table records are leaking in can-find statements
- I see nothing wrong with 10080a r15964.
Please proceed with testing (those from #8308 should do it) if the regress... - 05:04 AM Bug #10080 (Review): Temp-table records are leaking in can-find statements
- 05:02 AM Bug #10080 (WIP): Temp-table records are leaking in can-find statements
- Committed on 10080a, rev. *15964*.
The parameters where not updating in case there were a multiplex id injected in... - 08:05 AM Feature #10094 (WIP): RECIDs from different tenants of same logical database should not overlap
- During the runtime, the PKs even from different private tenants are unique across the logical database since all of t...
- 07:31 AM Feature #10094 (Test): RECIDs from different tenants of same logical database should not overlap
- 05:01 AM Feature #7020: always use "expanded" extent fields
- Radu tested @7020d@ with @<parameter name="expand-extents" value="false" />@ in @p2j.cfg.xml@ for the large GUI Appli...
06/03/2025
- 03:01 PM Bug #10083: Infinite loop when changing walking index fields
- I am not sure, but I think I made similar change in past and there was a problem. Let me check it with testcases/dirt...
- 01:47 AM Bug #10083 (Review): Infinite loop when changing walking index fields
- 01:46 AM Bug #10083 (WIP): Infinite loop when changing walking index fields
- With the patch from #10083-1, unit tests of a customer application does not get stuck in a infinite loop. Committed m...
- 04:05 AM Feature #7504: Export data tool from FWD into .d files
- Greg Shah wrote:
> Roger: Please review @export.sh@.
Roger, the revisions that need to be reviewed from @7504b@ a... - 03:44 AM Bug #10080: Temp-table records are leaking in can-find statements
- The scenario from #10076-1 is:...
06/02/2025
- 04:38 PM Bug #10083: Infinite loop when changing walking index fields
- Manage to create a small test case for infinite loop in unit tests in customer application. Please also look at the *...
- 04:37 PM Bug #10083 (Test): Infinite loop when changing walking index fields
- 02:50 PM Feature #7504: Export data tool from FWD into .d files
- Roger: Please review @export.sh@.
- 12:49 PM Feature #7504: Export data tool from FWD into .d files
- I added the support for exporting using @ant export.db@ .
The changes are in @build.xml@ and @build_db.xml@.
Sh... - 10:34 AM Feature #7504: Export data tool from FWD into .d files
- I created @export.sh@ and committed it to -@7504b / rev 15910@- @7504b / rev 15911@.
It it stored in @tools/script... - 09:16 AM Bug #10080: Temp-table records are leaking in can-find statements
- Original test case can be found in #8308-505. There are also more tests committed in xfer testcases/1753.
The chan... - 09:13 AM Bug #10080 (Test): Temp-table records are leaking in can-find statements
- 07:44 AM Feature #9440: get-codepage() function should work with CLOB fields
- Ok, thanks.
Related to this task, I noticed that the task status become "Internal Test".
What tests do I need to run? - 07:40 AM Feature #9440 (Internal Test): get-codepage() function should work with CLOB fields
- I'm OK with the changes.
05/31/2025
- 08:50 PM Feature #9456: implement SQL Server dialect and helpers
- Revision 15960 of 9456a contains the fix from #9456-6. It was successful on hotel import and (probably - technical is...
05/30/2025
- 01:33 PM Feature #9456: implement SQL Server dialect and helpers
- MSSQL has this syntax - see https://stackoverflow.com/questions/767657/how-do-i-create-a-unique-constraint-that-also-...
- 11:45 AM Feature #7504: Export data tool from FWD into .d files
- Right :(. It was my developer side talking :).
- 11:18 AM Feature #7504: Export data tool from FWD into .d files
- The ant target is only there when the conversion project is there. In production, it is not there, so the @export.sh...
- 11:05 AM Feature #7504: Export data tool from FWD into .d files
- My vote is for @ant@ target. It's more flexible and the configuration is already there (@build.properties@).
- 03:36 AM Feature #7504: Export data tool from FWD into .d files
- I think the best way to deliver this is through an @export.sh@ similar to @import.sh@ we already have.
You can also ...
05/29/2025
- 08:45 AM Feature #7504: Export data tool from FWD into .d files
- Ovidiu Maxiniuc wrote:
> I had a look at r15908 of 7504b.
>
> I noticed that the @main()@ method in @ExportWorker... - 08:05 AM Feature #9831 (Closed): add admin API to set c3p0 configuration for individual tenant databases
- Thanks, Brian!
- 07:53 AM Feature #9831: add admin API to set c3p0 configuration for individual tenant databases
- Testing now that all three RedMine issues are in place with the directory.xml removal of breakAfterAcquireFailure
ht...
05/28/2025
- 01:26 PM Feature #9456: implement SQL Server dialect and helpers
- To the list above I need to add another bullet:
* MSSQL does not allow multiple @null@ in unique indexes.
The solut... - 12:16 PM Feature #7504: Export data tool from FWD into .d files
- I had a look at r15908 of 7504b.
I noticed that the @main()@ method in @ExportWorker@ lacks the javadoc.
Also, ... - 07:22 AM Feature #7504: Export data tool from FWD into .d files
- Ovidiu Maxiniuc wrote:
> When I did the capture, I only looked up the occurrences, but did not do any further resear... - 10:05 AM Bug #10049 (Test): UDF configuration regression in Persistence.java
- Branch 10049a was merged into trunk as rev. 15946 and archived.
- 08:50 AM Bug #10049 (Merge Pending): UDF configuration regression in Persistence.java
- Please merge 10049a now.
- 03:10 AM Bug #9763 (Test): xml-node-name buffer option
- 9763b was merged to trunk rev. 15942 and archived.
- 03:00 AM Bug #9763 (Merge Pending): xml-node-name buffer option
- Eduard, you can merge 9763b now.
05/27/2025
- 03:53 PM Bug #10049: UDF configuration regression in Persistence.java
- *There is no new UDF added. Only a small runtime change.*
As noted in first note, the problem was an incorrect det... - 03:40 PM Bug #10049: UDF configuration regression in Persistence.java
- This is only a runtime change, with no new UDF installation (or other special handling/configuration or devops) requi...
- 03:18 PM Bug #10049: UDF configuration regression in Persistence.java
- The aforementioned test passed.
- 12:24 PM Feature #7504: Export data tool from FWD into .d files
- OK, you mentioned only 2 occurrences, but I knew that there are more calls of the method from the base class.
When... - 02:49 AM Feature #7504: Export data tool from FWD into .d files
- Ovidiu Maxiniuc wrote:
> I'm also on Idea and I see 35 of them. Maybe you have a filter of some kind?
> I cannot ex... - 09:55 AM Bug #9763: xml-node-name buffer option
- No, everything seems correct now.
- 06:00 AM Bug #9763: xml-node-name buffer option
- Review for 9763b rev 15950:
* BufferImpl - missing history number
* RecordBuffer - no actual change, use 'bzr rever... - 02:56 AM Feature #7020: always use "expanded" extent fields
- 7020d was rebased to latest trunk (rev. 15941) and it's now at revision 15959.
05/26/2025
- 05:37 PM Feature #9456: implement SQL Server dialect and helpers
- With my latest changes from 9456a, I was able to convert and import the @hotel@ database into a MS SQL Server instanc...
- 03:58 PM Bug #10049 (Internal Test): UDF configuration regression in Persistence.java
- OK, then I am putting this to the test.
This area is accessed each time a @Persistence@ object is initialized. The... - 02:22 PM Bug #10049: UDF configuration regression in Persistence.java
- I'm OK with the changes.
- 01:34 PM Bug #10049 (Review): UDF configuration regression in Persistence.java
- Constantin, please review the fix since it is a bit different (I rewrote 4 lines to be more human readable) than what...
- 01:32 PM Bug #10049 (Internal Test): UDF configuration regression in Persistence.java
- Constantin noticed a flaw in the configuration of UDF (SQL native vs deprecated Java). Just by chance, I identified t...
- 01:17 PM Bug #10049 (Test): UDF configuration regression in Persistence.java
- 12:15 PM Bug #9763: xml-node-name buffer option
- Fixed rebase issues in rev. 15950. Is additional testing necessary?
- 10:55 AM Bug #9763: xml-node-name buffer option
- I had one more quick look over 9763b, r15949.
In @BufferImpl.java@, I think there is a rebase error, @** 139 ES 2... - 08:19 AM Bug #9763: xml-node-name buffer option
- Eduard Soltan wrote:
> Yes it the 9763b branch, I run 9763b @bzr push --overwrite ~/secure/code/p2j_repo/p2j/active/... - 08:07 AM Bug #9763: xml-node-name buffer option
- Ovidiu Maxiniuc wrote:
> Do you mean 9763b? The current revision is 15835. Is it possible you pushed to different br... - 08:03 AM Bug #9763: xml-node-name buffer option
- Do you mean 9763b? The current revision is 15835. Is it possible you pushed to different branch?
- 07:58 AM Bug #9763: xml-node-name buffer option
- Rebased to latest trunk, *rev. 15937*. Did some quick smoke testing and unit tests of a large GUI application and it ...
- 11:14 AM Feature #7504: Export data tool from FWD into .d files
- I'm also on Idea and I see 35 of them. Maybe you have a filter of some kind?
I cannot export this list so I attached... - 08:16 AM Feature #7504: Export data tool from FWD into .d files
- I've reviewed the usages of @toStringExport()@:
* Within the @raw@ class: it's only used in @toString()@, which can ... - 07:56 AM Feature #7504: Export data tool from FWD into .d files
- +Review of 7504b / r15907+
I think there might be some issues with current changes from @raw@ class. The problem i... - 07:28 AM Feature #7504: Export data tool from FWD into .d files
- Ovidiu Maxiniuc wrote:
> +Review of 7504b / r15906+
>
> * @raw.java@: The problem is that the @toStringExport()@ ... - 05:23 AM Feature #9543 (Test): implement missing BUFFER attributes
- 9543b was merged to trunk 15936 and archived.
- 04:43 AM Feature #9543 (Merge Pending): implement missing BUFFER attributes
- Please merge 9543b after 10027a
- 01:32 AM Feature #9543: implement missing BUFFER attributes
- Ovidiu Maxiniuc wrote:
> I think the update is safe.
>
> But, before the merge into trunk, please add the followi...
05/23/2025
- 04:06 PM Feature #9543: implement missing BUFFER attributes
- I think the update is safe.
But, before the merge into trunk, please add the following changes (no code affected, ... - 05:30 AM Feature #9543: implement missing BUFFER attributes
- Some additional testing should be performed or it could merged to trunk?
- 12:34 AM Feature #9543: implement missing BUFFER attributes
- Summary of the testing performed:
- unit tests and smoke tests of large GUI appplication ✅
- smoke tests of a ... - 03:02 PM Feature #7504: Export data tool from FWD into .d files
- +Review of 7504b / r15906+
Good job. Just some minor issues:
* @Record.java@:2099: a space is required after @if@... - 07:32 AM Feature #7504: Export data tool from FWD into .d files
- Thanks for the review, Ovidiu.
Sorry for the formatting issues, i've addressed all of them in rev @15906@.
> * ... - 12:40 PM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Will the addition of this parameter in @p2j.cfg.xml@ break conversion if #7020 fix is not in... - 12:37 PM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> Yes, that's correct.
Thanks. I have this in the @p2j.cfg.xml@ I will check into the p... - 12:28 PM Feature #7020: always use "expanded" extent fields
- Roger Borrello wrote:
> Stefanel Pezamosca wrote:
> > The thing changed in 7020d is the @denorm-extents@ from @p2j.... - 12:23 PM Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> The thing changed in 7020d is the @denorm-extents@ from @p2j.cfg.xml@ that was renamed w... - 11:15 AM Feature #7020: always use "expanded" extent fields
- Alexandru Lungu wrote:
> > Does 7020d remove normalized extent support completely? If so, then we have to resolve #7... - 10:51 AM Feature #7020: always use "expanded" extent fields
- Greg Shah wrote:
> Is there any reason to hold back 9537a? Has it been tested enough?
Yes 9537a has been tested an... - 10:27 AM Feature #7020: always use "expanded" extent fields
- > Does 7020d remove normalized extent support completely? If so, then we have to resolve #7020-122 before we merge. O...
- 09:10 AM Feature #7020: always use "expanded" extent fields
- Greg Shah wrote:
> > I think such process should be documented and create a task per customer (for us to test).
>
... - 09:07 AM Feature #7020: always use "expanded" extent fields
- > I think such process should be documented and create a task per customer (for us to test).
Agreed.
It is my u... - 08:38 AM Feature #7020: always use "expanded" extent fields
- > Are there any other tests that should be done for 7020d?
Stefanel, from my understanding, 7020d is making any sc...
Also available in: Atom