Radu Apetrii's activity
From 10/12/2024 to 11/10/2024
11/09/2024
- 05:57 PM Database Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> Committed on 9267a, rev. 15541.
Well, my 9267a only goes to revision 15527. Are we facing an...
11/06/2024
- 07:02 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- Radu Apetrii wrote:
> Rev. 15533 seems to be with things from the trunk, but please correct me if I'm wrong.
Or not... - 06:33 AM Database Feature #9057: enable intermixed access to default tenant (shared) data and tenant-specific data
- I assume the revisions that need reviewing are 15526-15532 inclusively. Rev. 15533 seems to be with things from the t...
11/05/2024
- 03:04 PM Database Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> I committed on 9267a, rev. 15531.
Eduard, are you sure the branch was bound when you commit... - 07:51 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> > * Radu: I'll look into #9267-36 and see what I can deduce.
>
> If you need more assistan... - 07:48 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- First of all, don't ask me what I searched to get to this pdf. Secondly, it seems that we were right: persistent tabl...
- 06:48 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Eduard Soltan wrote:
> Radu Apetrii wrote:
>
> > I think we're going to need an example for each of these cases. ... - 06:40 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Alexandru Lungu wrote:
> > OK, an update to this: I believe the alphabetical order is for the "static" index definit... - 06:32 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- I've also added Eric as a watcher to this discussion. I don't know why he wasn't here in the first place.
- 06:30 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Radu Apetrii wrote:
> Does this mean that the order in which we define the indexes is the tie-breaker here? If so, ...
11/04/2024
- 09:23 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Constantin Asofiei wrote:
> There are documented rules for index selection here: [[p2j:Chapter_27_Sorting_Query_Resu... - 06:41 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- OK, so, here's the testcase:
Table definition:
{{collapse... - 02:58 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- Eduard: I got informed by a customer of a query that uses the wrong index now (with the 9267a changes), and was using...
11/01/2024
- 07:55 AM Database Bug #9267: Index Selection in case of a multiple index matches.
- I finished testing another customer application. The result is positive, everything went fine. ✅
10/30/2024
- 07:25 AM Database 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.
...
10/29/2024
- 09:45 AM Database 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 Database 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 ...
10/25/2024
- 09:05 AM Database 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...
10/15/2024
- 07:52 AM User Interface Bug #8239: SELECTION-LIST set SCREEN-VALUE regression from trunk rev. 14821
- Hynek Cihlar wrote:
> Radu, what issue/task branch resolved this?
It was trunk revision 15114 that fixed the issue.
10/14/2024
- 04:06 AM User Interface Bug #8239: SELECTION-LIST set SCREEN-VALUE regression from trunk rev. 14821
- I re-checked this, and it was solved in the meantime. It can be closed.
Also available in: Atom