Ovidiu Maxiniuc's activity
From 10/29/2024 to 11/27/2024
11/28/2024
- 10:30 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Committed revision 15600 of 9057a. It contains the changes noted in above discussion (review).
11/27/2024
- 05:19 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Eric Faulhaber wrote:
> * I reviewed the changes, but it is hard to review for possible missing changes, such as pla... - 01:37 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Never done, in the new format. I will try to.
- 12:39 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- I've just done that. Committed revision 15599.
I wanted to test them but for some strange causes, the project fail... - 08:38 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Status update:
* I addressed the issues reported by Constantin in note #9057-38 and Alexandru in #9057-39. Committe... - 09:34 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Added TRPL documentation on MT processing.
Committed revision 15597.
11/26/2024
- 12:33 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Done. I did a quick smoke test to check at least it compiles correctly.
I am going on with tests as described in #90... - 11:30 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Alexandru,
Thank you for reporting this.
I encountered similar issue when I did some tests with the large applicat... - 09:27 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Eric Faulhaber wrote:
> Ovidiu, don't you need to rebase the branch?
I've just done the rebase. The current revisio... - 08:16 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- I think I have finished the multi-tenant specific implementation. The latest commit is 15586 in branch 9057a.
Since ...
11/23/2024
- 10:15 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Yesterday I implemented the runtime support for the @setMultiTenantAlternative()@ to be method injected in case of po...
11/21/2024
- 07:59 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Greg Shah wrote:
> > a new set of FindQuery APIs which would accept both tuple of (fql, client-where, args). I think... - 06:09 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Yes, I did think of something like that, but since it involved changes in generated code, I kept it a plan B.
Ther... - 07:45 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Update on my latest effort to get done the last known multiple-tenant issue described above.
The compound queries ...
11/20/2024
- 09:55 AM Base Language Bug #6389: LENGTH function with COLUMN option
- I am sorry, I forgot to add the 'destination' parameter for @chr@ function. I updated the procedures above. It turn o...
- 09:10 AM Base Language Bug #6389: LENGTH function with COLUMN option
- I extended the extractor to:...
- 08:49 AM Base Language Bug #6389: LENGTH function with COLUMN option
- To extract the column lengths for all 64Ki Unicode characters we can use the following procedure (do not forget to st...
- 07:59 AM Base Language Bug #6389: LENGTH function with COLUMN option
- Artur Școlnic wrote:
> Ovidiu, won't manually scanning the Unicode planes for any type of characters limit the funct...
11/19/2024
- 12:51 PM Base Language Bug #6389: LENGTH function with COLUMN option
- Eugenie Lyzenko wrote:
> However the main question here I think is to detect what is the output of the @LENGTH@ in 4... - 12:44 PM Base Language Bug #6389: LENGTH function with COLUMN option
- +Review of 6389a/15563+
The solution seems close, but there are some issues we need to discuss:
* your sample in ...
11/18/2024
- 05:02 PM Database Feature #7020: always use "expanded" extent fields
- Greg Shah wrote:
> Ovidiu: What is the list of remaining work/testing to finish this task?
I have committed revis... - 08:08 AM Database Feature #7020: always use "expanded" extent fields
- Stefanel Pezamosca wrote:
> I have locally rebased 7020b branch to trunk revision 15561. @./gradlew all@ works, but ... - 08:44 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- I have committed a new revision of 9057a (r15574, was rebased to trunk 15560).
It contains clarifications for all ...
11/13/2024
- 08:55 PM Database Feature #9057 (WIP): enable intermixed access to default tenant (shared) data and tenant-specific...
- I have committed a new incremental revision on 9057a (r15555).
Changes:
* the buffers are re-initialized (their per...
11/08/2024
- 09:03 PM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Eric Faulhaber wrote:
> Code review 9057a/15544-15551:
Thank you for the quick review.
> General question: throu...
11/07/2024
- 10:29 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- I have rebased the branch successfully. The current revision is 15551, based on trunk 15543.
Ready for review, but p... - 09:08 PM Database Bug #9267: Index Selection in case of a multiple index matches.
- I looked at 9267a, rev. 15525/6, but I have some difficulties understanding the logic. I will go deeper tomorrow.
...
11/06/2024
- 07:47 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Radu Apetrii wrote:
> Or not. Next to the revision number there was a @[merge]@, and I assumed it came from trunk, b... - 07:29 PM Database Bug #9267: Index Selection in case of a multiple index matches.
- I checked the devsrv01, the last revision of 9267a is indeed 15524, from 2024-10-30.
11/05/2024
- 09:15 AM Database Feature #9057 (Review): enable intermixed access to default tenant (shared) data and tenant-speci...
- I added intermixed access support for some of the methods above. In fact only for those where I was able to identify ...
11/02/2024
- 09:33 PM Database 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
- 01:21 PM Database 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/31/2024
- 07:53 PM Database 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...
10/30/2024
- 11:50 AM Database 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 ...
10/29/2024
- 03:08 PM Database 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...
Also available in: Atom