unexpected query result

[Hilaire Fernandes]

I tried the abort, still same.
Then I did your check and I got 0 in all case, vet confusion. I may have 
a bad use of index but I have not found it yet.

Hilaire



Chris Muller a écrit :
> That does look strange.  Do you have uncommitted adds to this
> MagmaSet?  I.e., if you do an abort do you still get these same
> numbers?
> 
> If so, the first step is to discover for sure what is in the index.
> In the server image, navigate from the MagmaRepositoryController to
> the particular MaHashIndex (the -oids.hdx one).  The path is something
> like:
> 
>  repository -> largeCollectionManagers -> [oid] -> keyIndexesByAttribute 
> -> #id
> 
> and ask it:
> 
>  self occurrencesOf: 103654912
> 
> and
> 
>  self numberOfEntriesFrom: 103654912 to: self highestPossibleKey
> 
> And make sure you get consistent #'s there.  If so, try starting a new
> MagmaSession.  If not, it may be necessary to rebuild that index..
> 
> 
> 
> On 4/5/07, Hilaire Fernandes <hilaire2006 at laposte.net> wrote:
>> I have this unexpected result from a MagmaSet query, where id is an
>> Integer index:
>>
>> (learners where: [:l | l id > 103654912]) size
>> =>2
>>
>> (learners where: [:l | l id >= 103654912]) size
>> =>3
>>
>> (learners where: [:l | l id = 103654912]) size
>> =>0
>>
>> Also I am sure object with id = 103654912 is in the MagmaSet.
>>
>> Index problem?
>>
>> _______________________________________________
>> Magma mailing list
>> Magma at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/magma
>>