Activity
From 10/04/2024 to 11/02/2024
11/02/2024
- 09:33 PM Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> Conversion of a customer GUI application finished successfully. Also tested unit tests, with ...
11/01/2024
- 04:29 PM Feature #7020: always use "expanded" extent fields
- Ovidiu Maxiniuc wrote:
> I understand now. The problem is @display ttw.f1[i] with frame f3.@. Note the variable @i@ ... - 01:21 PM Feature #7020: always use "expanded" extent fields
- I understand now. The problem is @display ttw.f1[i] with frame f3.@. Note the variable @i@ as index in @ext1b.p@ as o...
- 10:08 AM Feature #7020: always use "expanded" extent fields
- Ovidiu Maxiniuc wrote:
> Does the build fail because of the missing accessors?
This is the compilation error:
<p... - 10:27 AM Bug #9267: Index Selection in case of a multiple index matches.
- I finished testing another customer application after reconversion. Results of unit tests and smoke testing GUI are p...
- 07:55 AM Bug #9267: Index Selection in case of a multiple index matches.
- I finished testing another customer application. The result is positive, everything went fine. ✅
- 02:42 AM Bug #9267: Index Selection in case of a multiple index matches.
- Conversion of a customer GUI application finished successfully. Also tested unit tests, with no regression.
Pushed... - 09:53 AM Bug #9078 (Review): emit FindQuery as (reused) variables
- Constantin, as discussed, please review the changes when you have time.
- 07:06 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15537*. Fixed wrong order of emitted FindQuery variable.
- 05:57 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15536*.
* Only emit a FindQuery as a variable for looping inner blocks.
* Fixed #9032-42.
* Cl...
10/31/2024
- 07:53 PM Feature #7020: always use "expanded" extent fields
- Roger,
I looked at the code. I do not see what the problem is. The only difference which is probably visible in ap... - 04:00 PM Feature #7020: always use "expanded" extent fields
- Constantin provided a simple example in #8805-64 where this is in a persistent DB:...
- 11:02 AM Bug #9078: emit FindQuery as (reused) variables
- I've managed to get a stable conversion with the new changes, but I found this case that needs to be investigated:
<...
10/30/2024
- 02:18 PM Bug #9267: Index Selection in case of a multiple index matches.
- Made the necessary changes on 9267a, revision 15524.
I will redo the conversion of a customer application this eve... - 11:50 AM Bug #9267 (Internal Test): Index Selection in case of a multiple index matches.
- +Review of 9267a r15523.+
I must admit it is strange that simple find queries and 'looping' queries use different ... - 08:01 AM Bug #9267: Index Selection in case of a multiple index matches.
- Radu Apetrii wrote:
> I'm gonna assume that I need to re-run the conversion for that customer application. I've alre... - 07:25 AM Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> I made some changes to reflect behaviour from #9267-20 in 9267a, rev. 15523. Please review.
... - 07:16 AM Bug #9267: Index Selection in case of a multiple index matches.
- I made some changes to reflect behaviour from #9267-20 in 9267a, rev. 15523. Please review.
- 03:46 AM Bug #9267: Index Selection in case of a multiple index matches.
- Ovidiu Maxiniuc wrote:
> I did analyse at the sources posted on devsrv01. Definitely, the ones generated by 9267a lo... - 10:15 AM Bug #9078: emit FindQuery as (reused) variables
- Constantin Asofiei wrote:
> Danut, the @FindQuery@ var def should be similar to the @OPEN QUERY@ var def - see @con... - 10:02 AM Bug #9078: emit FindQuery as (reused) variables
- Danut, the @FindQuery@ var def should be similar to the @OPEN QUERY@ var def - see @convert/database_access.rules@ a...
- 06:06 AM Bug #9078: emit FindQuery as (reused) variables
- Constantin Asofiei wrote:
> Dănuț Filimon wrote:
> > Constantin, at this point the conversion changes for #9032-2 a... - 05:53 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> Constantin, at this point the conversion changes for #9032-2 are implemented, but during yest... - 05:37 AM Bug #9078: emit FindQuery as (reused) variables
- Rebased *9078a* with *trunk/15526*, the branch is now at revision *15535*.
- 05:25 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15525*.
* FIND statements are annotated using "fqryname" annotation instead of "qryname". Because t...
10/29/2024
- 03:08 PM Bug #9267: Index Selection in case of a multiple index matches.
- Review of 9267a, r15522.
The changes do make sense. Please add the H entry.
I did analyse at the sources posted... - 10:14 AM Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> Please review 9267a, rev. 15522.
>
> I have tests with regression changes project, and a l... - 10:07 AM Bug #9267 (Review): Index Selection in case of a multiple index matches.
- Please review 9267a, rev. 15522.
I have tests with regression changes project, and a large customer GUI app. The r... - 10:04 AM Bug #9267 (WIP): Index Selection in case of a multiple index matches.
- 09:51 AM Bug #9267: Index Selection in case of a multiple index matches.
- Radu Apetrii wrote:
> The point here is that @idx2@ and the @WHERE@ clause share a prefix of fields, but they are no... - 09:45 AM Bug #9267: Index Selection in case of a multiple index matches.
- So, I've attached the @.df@ used. It's a basic @test@ persistent table with three indexes: one primary unique one (wh...
- 09:31 AM Bug #9267: Index Selection in case of a multiple index matches.
- Sure, go ahead.
- 09:31 AM Bug #9267: Index Selection in case of a multiple index matches.
- It seems that 9267a fixes my issue from #8357-140. Eduard, if you want, I can post here a small testcase with what I ...
- 08:54 AM Bug #9267: Index Selection in case of a multiple index matches.
- Added my testcases on @tests/query/index/IndexSelectionExactMatching.cls@.
Out of 13 tests:
- 6 test fails with... - 07:34 AM Bug #9078: emit FindQuery as (reused) variables
- Fixed #9078-33 in *9078a/15524*.
- 05:00 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15523*. Added the fix mentioned in #9078-32.
- 04:46 AM Bug #9078: emit FindQuery as (reused) variables
- This one also:...
- 04:42 AM Bug #9078: emit FindQuery as (reused) variables
- I found a new fix for #9078-28, after converting hotel_gui and comparing the old and new conversions, I found the fol...
- 03:16 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> 9078a/15521 commit reverts most of the effort done for 9078a. I will have to think of another...
10/28/2024
- 10:08 AM Bug #9078: emit FindQuery as (reused) variables
- 9078a/15521 commit reverts most of the effort done for 9078a. I will have to think of another solution.
- 09:44 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> Dănuț Filimon wrote:
> > I discovered a new conversion issue while testing hotel_gui so I am... - 06:51 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> I discovered a new conversion issue while testing hotel_gui so I am currently investigating i... - 06:41 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15520*. Modified CAN-FIND conversion to match the FIND statement conversion.
I discovered a new c... - 04:12 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15519*. Support FindQuery constructor conversion as a variable scoped to the top level block.
TOD... - 03:06 AM Bug #7496: finish support for query:forward-only attribute
- *7496a* can be merged.
10/25/2024
- 09:49 AM Bug #7496: finish support for query:forward-only attribute
- Rebased *7496a* with *trunk/rev.15523*. *7496a* is now at revision *15534*.
- 09:36 AM Bug #7496: finish support for query:forward-only attribute
- After retesting, performance is not affected. (-1% from baseline)
- 08:59 AM Bug #7496: finish support for query:forward-only attribute
- I updated the test plan status from #7496-76 with the latest results. The test plan was completed and there were no r...
- 06:44 AM Bug #7496: finish support for query:forward-only attribute
- I applied the changes over 7156c rev. 15501. I will redo the testing today, I will update when they are done. ETA: 3h.
- 03:58 AM Bug #7496: finish support for query:forward-only attribute
- Ioana-Cristina Prioteasa wrote:
> Applied 7496 changes over 7156c. The total time for a performance round has gone f... - 09:23 AM Bug #9267: Index Selection in case of a multiple index matches.
- Radu, let me do you one better: https://proj.goldencode.com/artifacts/javadoc/latest/api/com/goldencode/p2j/schema/pa...
- 09:05 AM Bug #9267: Index Selection in case of a multiple index matches.
- If needed, there is also this wiki page "Index Selection":https://proj.goldencode.com/projects/p2j/wiki/Chapter_27_So...
- 04:11 AM Bug #9267: Index Selection in case of a multiple index matches.
- Alexandru Lungu wrote:
> Eduard, can you augment the xfer testcases on index_selection with some of your findings an... - 04:11 AM Bug #9267: Index Selection in case of a multiple index matches.
- Eduard, can you augment the xfer testcases on index_selection with some of your findings and test that as well: make ...
- 03:58 AM Bug #9267: Index Selection in case of a multiple index matches.
- I comitted my change on 9267a, rev. 15522.
With this change, in *findLeadingIndexMatch* in case we have multiple i... - 02:41 AM Bug #9267: Index Selection in case of a multiple index matches.
- > Looking at calcIndexSelection it will always return a single index. Do you know whether that is intentional or sele...
- 08:03 AM Bug #9078: emit FindQuery as (reused) variables
- I've managed to find a fix for #9078-22, it involved searching for a top level block that has a top level ancestor an...
- 07:17 AM Bug #9078: emit FindQuery as (reused) variables
- I've managed to fix #9078-21, there was another rule whre the FindQuery constructor was created so I had to change it...
- 03:01 AM Bug #9078: emit FindQuery as (reused) variables
- I have trouble differentiating between the top block execute method and top block class method. Because of #9078-20 a...
- 07:26 AM Bug #9034: FindQuery unique fails in a self join context
- I committed 9034a_h2/53, it addressed the review points from #9034-12 and the issue discussed in #9034-17.
deleted - 06:13 AM Bug #9034: FindQuery unique fails in a self join context
- This is how the code looked before any FWD-H2 specific changes:...
- 05:24 AM Bug #9034: FindQuery unique fails in a self join context
- Alexandru, during testing of 9134a_h2, I encountered some issue with the @next@ method in @TreeCursor@:...
- 03:30 AM Bug #9034: FindQuery unique fails in a self join context
- > Review of 9034a:
These were change local on my side, ignore review.
10/24/2024
- 09:39 AM Bug #9267: Index Selection in case of a multiple index matches.
- ...
- 07:51 AM Bug #9078: emit FindQuery as (reused) variables
- Another known problem where the FindQuery is not properly converted:...
- 07:15 AM Bug #9078: emit FindQuery as (reused) variables
- Alexandru Lungu wrote:
> I am not sure if the FindQuery should be generated as a class member anyway. Its scope can ... - 07:07 AM Bug #9078: emit FindQuery as (reused) variables
- I am not sure if the FindQuery should be generated as a class member anyway. Its scope can remain there. Otherwise, f...
- 07:06 AM Bug #9078: emit FindQuery as (reused) variables
- Committed *9078a/15518*. Added a default constructor for FindQuery so that the converted code compiles.
- 06:50 AM Bug #9078: emit FindQuery as (reused) variables
- The issue was related to adding an annotation to @this@ and not @copy@, after this I managed to make a few more chang...
- 04:31 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> I am currently working on adding a "qryname" annotation to each find query (not just for the ... - 03:14 AM Bug #9078: emit FindQuery as (reused) variables
- I am currently working on adding a "qryname" annotation to each find query (not just for the AdaptiveFind) but I am f...
- 03:55 AM Bug #7496: finish support for query:forward-only attribute
- Applied 7496 changes over 7156c. The total time for a performance round has gone from *38.4s to 44.1s, 14% slowdown.*...
10/23/2024
- 09:02 AM Bug #9274: Analyze how creatingBuffer is relevant after the introduction of multiplyReferenced DMOs
- This task is about the relevance of @RecordBuffer.creatingBuffer@.
Recently, FWD added support for multiplyReferen... - 08:45 AM Bug #9274 (New): Analyze how creatingBuffer is relevant after the introduction of multiplyReferen...
- 05:33 AM Bug #7496: finish support for query:forward-only attribute
- Alexandru Lungu wrote:
> I am OK with the changes in rev. 15505.
> Please also run performance tests - contact [icp... - 05:22 AM Bug #7496 (Internal Test): finish support for query:forward-only attribute
- I am OK with the changes in rev. 15505.
Please also run performance tests - contact [icp] for the performance tests ... - 05:01 AM Bug #7496: finish support for query:forward-only attribute
- Testing finished successfully:
* Smoke test 3 GUI application
* Harness test
* 2 customer unit tests
Testing le... - 05:28 AM Bug #9034 (WIP): FindQuery unique fails in a self join context
- Review of 9034a:
* remove oo imports from RAQ
* add history entry for @DirectAccessHelper@
* remove changes from E... - 05:16 AM Bug #9078: emit FindQuery as (reused) variables
- I think I get it ... there is no link between the columns. So on line 1, there are actual 3 different find queries.
... - 04:33 AM Bug #9078: emit FindQuery as (reused) variables
- Alexandru Lungu wrote:
> What does first place mean? Is the same FIND Query 1022 times in a constructor, 111403 in a... - 04:21 AM Bug #9078: emit FindQuery as (reused) variables
- What does first place mean? Is the same FIND Query 1022 times in a constructor, 111403 in an execute and 883905 in an...
- 03:59 AM Bug #9078: emit FindQuery as (reused) variables
- After a retest of the scenario mentioned in #9078, I managed to gather the following information:
* Instances create...
10/22/2024
- 07:49 AM Bug #9078: emit FindQuery as (reused) variables
- After a quick analysis I found the following:
* Instances created: *6900539*
* Instances created in a constructor c... - 05:10 AM Bug #9078: emit FindQuery as (reused) variables
- Dănuț Filimon wrote:
> * A part of the analysis can be done on the converted code (how many FindQuery instances can ... - 04:27 AM Bug #9078: emit FindQuery as (reused) variables
- My plan is to analyze a customer application (using a test scenario) for:
* The number of total FindQuery instances ... - 03:48 AM Bug #9078 (WIP): emit FindQuery as (reused) variables
- 06:26 AM Bug #7496: finish support for query:forward-only attribute
- I finished running the unit tests of a customer and found 2 tests regressing in 2 modules, but after retesting with @...
- 01:21 AM Bug #7496: finish support for query:forward-only attribute
- I've started testing 7496a using the unit tests of a customer last night and it got stuck on a module (infinite loop)...
10/21/2024
- 05:57 PM Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- New update.
I am advancing with identifying and choosing the right physical database when some API from persistenc... - 07:57 AM Bug #7496 (Review): finish support for query:forward-only attribute
- *Committed 7496a/15505*. Fixed error handling for static and dynamic queries, removed unnecessary boolean parameter. ...
- 07:37 AM Bug #7496: finish support for query:forward-only attribute
- Dănuț Filimon wrote:
> The @queryForward()@ method does not take into account that the query might be closed, the er... - 07:27 AM Bug #7496: finish support for query:forward-only attribute
- The following example:...
- 07:03 AM Bug #7496 (WIP): finish support for query:forward-only attribute
- I'll put the issue in WIP a bit until I am done investigating #7496-66.
- 07:01 AM Bug #7496: finish support for query:forward-only attribute
- Oh I see, it is a difference on the method called - you are right.
- 06:58 AM Bug #7496: finish support for query:forward-only attribute
- Alexandru Lungu wrote:
> * There are some places where @ ErrorManager.recordOrShowError(3159, String.format(errMsg, ... - 06:43 AM Bug #7496: finish support for query:forward-only attribute
- Review of #7496:
* I am OK with the changes
* There are some places where @ ErrorManager.recordOrShowError(3159, St... - 06:35 AM Bug #7496: finish support for query:forward-only attribute
- I started investigating the failing tests and made the following change:...
- 06:08 AM Bug #7496 (Review): finish support for query:forward-only attribute
- Alexandru Lungu wrote:
> It is normal to have the same number of P2J queries. In an @AdaptiveQuery@ it either choose... - 06:01 AM Bug #7496: finish support for query:forward-only attribute
- It is normal to have the same number of P2J queries. In an @AdaptiveQuery@ it either chooses to use @ProgressiveResul...
- 05:53 AM Bug #7496: finish support for query:forward-only attribute
- I compared the p2j-query__temp.log of the Startup + warmup + 5 runs of the extented performance scenario of a custome...
10/18/2024
- 02:25 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- > Good catch. Stefanel: please add check at the top of FQLPreprocessor.translate, if the where clause is null, just e...
10/17/2024
- 11:51 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- Ovidiu Maxiniuc wrote:
> # the synchronization. In @AbstractQuery.translateSort()@ and also in @FQLPreprocessor.tran... - 11:39 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- Stefanel Pezamosca wrote:
> I committed to *revision 15501*: Added caching for translateSort(RecordBuffer, RecordBuf... - 03:41 AM Bug #9251 (Test): cache the translated FQL in FQLPreprocessor.translate
- Branch 9251a was merged into trunk as rev. 15503 and archived.
- 03:12 AM Bug #9251 (Merge Pending): cache the translated FQL in FQLPreprocessor.translate
- The changes look good. I've ran ETF and #9214 and they are OK.
You can merge to trunk now. - 09:23 AM Bug #7496: finish support for query:forward-only attribute
- This is really good stuff, Danut!
- 08:53 AM Bug #7496: finish support for query:forward-only attribute
- Good news! I've expanded the unit tests and included the adaptive tests (that use temp-tables) after rewriting them a...
- 09:10 AM Bug #9267: Index Selection in case of a multiple index matches.
- The following change drove down the change in @IndexSelectionWorker@ from trunk/ rev. 15486:...
- 08:33 AM Bug #9267 (Test): Index Selection in case of a multiple index matches.
10/16/2024
- 08:46 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- I committed to *revision 15501*: Added caching for translateSort(RecordBuffer, RecordBuffer, String) output.
Please ... - 07:10 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- Stefanel Pezamosca wrote:
> First try: it seems like caching the @translateSort@ output does not bring any improveme... - 06:52 AM Bug #9251 (Review): cache the translated FQL in FQLPreprocessor.translate
- First try: it seems like caching the @translateSort@ output does not bring any improvements.
Please review the tra... - 04:54 AM Bug #9251 (WIP): cache the translated FQL in FQLPreprocessor.translate
- I have created *branch 9251a* from *trunk revision 15498*.
I committed to *revision 15499* the implementation for ca... - 05:25 AM Bug #9262: batch assign updates the dirty database on each assignment
- Yes, in 7156c the @RecordNursery@ will hold onto all inserts/updates till the first query will occur. This is how tru...
- 05:01 AM Bug #9262 (Hold): batch assign updates the dirty database on each assignment
- Yes, with 7156c @DirtyShareContext.insert@ is being called on batch end, so assuming the changes in 7156c will reach ...
- 04:17 AM Bug #9262: batch assign updates the dirty database on each assignment
- Can you do a similar test with 7156c? 7156c has a reword of @RecordNursery@ and how the dirty changes are registered....
- 03:32 AM Bug #9262: batch assign updates the dirty database on each assignment
- I found some cases where @DirtyShareContext.insert@ is being called on each assignment in a batch assign, and not jus...
- 03:27 AM Bug #9262 (Hold): batch assign updates the dirty database on each assignment
10/15/2024
- 08:35 AM Bug #7641: Lower the number of Map.get() calls in the persistence layer
- I have created branch 7641b (trunk 15494). At the moment I managed to extract mostly all the changes from 7641a (e.g....
- 07:20 AM Bug #7641 (WIP): Lower the number of Map.get() calls in the persistence layer
- > So, I tried to rebase, but I get that error with key already present in map. devsrv01 is too slow to do the rebase ...
- 07:59 AM Bug #7496: finish support for query:forward-only attribute
- I've managed to create unit tests based on the tests I've had for this issue (there were a lot more compared to what ...
- 06:28 AM Bug #7496: finish support for query:forward-only attribute
- I am currently working on replacing the old tests for this issue with unit tests.
10/14/2024
- 06:44 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- The recreate is this:...
- 06:26 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- > Alexandru: can you add this to the existing sprint?
Ok; do you have a small test-case in which that part of code... - 06:09 AM Bug #9251: cache the translated FQL in FQLPreprocessor.translate
- We need a LRU cache for the @FQLPreprocessor.translate@ result. The cache key will be similar to existing FQL keys, ...
- 06:07 AM Bug #9251 (Test): cache the translated FQL in FQLPreprocessor.translate
10/11/2024
- 10:56 AM Bug #7641: Lower the number of Map.get() calls in the persistence layer
- So, I tried to rebase, but I get that error with key already present in map. devsrv01 is too slow to do the rebase th...
- 04:40 AM Bug #7641: Lower the number of Map.get() calls in the persistence layer
- Stefanel, please recap #7641 effort, rebase 7641a and review.
After, lets do some performance testing with it to und... - 04:14 AM Bug #7641: Lower the number of Map.get() calls in the persistence layer
- Constantin - I wanted to remember you of this task, considering you have worked recently on performance matters. 7641...
- 08:03 AM Bug #7496: finish support for query:forward-only attribute
- Rebased *7496a* with *trunk/rev.15494*. *7496a* is now at revision *15504*.
10/09/2024
- 10:53 AM Bug #9194: FWD selects the wrong index when using CONTAINS?
- It's time for another blast from the past (maybe?). I'm going to take all of you back to #1587 (the ticket, not the y...
- 09:19 PM Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- The current solution I am trying to make it work is as follows:
* each @Database@ object should have a reference to ...
10/08/2024
- 09:20 AM Bug #9194: FWD selects the wrong index when using CONTAINS?
- I have created 9194a for further changes. First, I'll check why the word-index is not selected. After that, I'll see ...
- 02:03 AM Bug #9194: FWD selects the wrong index when using CONTAINS?
- OK, thank you for your response and the one previous about the projects (I hadn't been made aware of this).
- 09:08 AM Bug #9228: FQL to SQL conversion for CONTAINS when the output is expected to be always false is n...
- Please update [[regression:Open Regressions in FWD v4]] with the status.
- 03:28 AM Bug #9228 (Test): FQL to SQL conversion for CONTAINS when the output is expected to be always fal...
- Branch 9228a was merged to trunk rev 15483 and archived.
- 02:02 AM Bug #9228 (Merge Pending): FQL to SQL conversion for CONTAINS when the output is expected to be a...
- Stefanel Pezamosca wrote:
> I had the changes patched to my local trunk for a while now. I didn't encounter any obvi...
10/07/2024
- 07:15 PM Bug #9194: FWD selects the wrong index when using CONTAINS?
- Eric Faulhaber wrote:
> Andy Edwards wrote:
> > [...] FWD will not use the same WORD-INDEX rules as the 4GL so we w... - 03:03 PM Bug #9194: FWD selects the wrong index when using CONTAINS?
- Andy Edwards wrote:
> Hi all, we have completed the "indeterminate sorting" review and are now starting to make the ... - 10:11 AM Bug #9228: FQL to SQL conversion for CONTAINS when the output is expected to be always false is n...
- I had the changes patched to my local trunk for a while now. I didn't encounter any obvious issues while testing.
- 05:13 AM Bug #9228: FQL to SQL conversion for CONTAINS when the output is expected to be always false is n...
- Stefanel, please go ahead and test other projects. If they are OK, we can queue this for merge.
10/04/2024
- 05:52 AM Bug #9194: FWD selects the wrong index when using CONTAINS?
- Hi all, we have completed the "indeterminate sorting" review and are now starting to make the necessary changes, henc...
- 03:42 AM Bug #9228: FQL to SQL conversion for CONTAINS when the output is expected to be always false is n...
- I've tested ETF and is OK. I think we need to wait for 6667i to be merged, and after that we'll test some other apps...
Also available in: Atom