MagmaCollectionReader behavior

[Miguel Cobá]

2009/4/1 Keith Hodges <keith_hodges at yahoo.co.uk>:
>
>>
>> I think that this is a point where the requirements for the developers
>> can be a little too much. See it this way, we are only indexing a
>> string. It shouldn't be necessary to implement a hash code for
>> converting them to numbers. Besides, most of us, or at least me, are
>> not experts in the hashing techniques and for sure we can't be certain
>> that the hash is correct or that don't clash.
>>
>>>
>>> If you want to use a big, fat, e-mail address as a "unique
>>> identifier", you will be better served to use most of a 64 or 128-bit
>>> key-space than a small percentage of a 400-bit key-space.  Using only
>>> the alpha range:
>>>
>>>     (MaSearchStringIndex attribute: #email) keySize: 128; beAlpha;
>>> yourself
>>
>> This line it is perfect for the wiki page, instead of the current one,
>> because it will give the expected results most of the time. Of course
>> the note about the limit cases should be present.
> My Bad,
>
> I threw that code together in a rushed weekend a long time ago and
> thought no more of it, it worked, but then I only had 3 records!
>
> Please do feel free to update the wiki page with improvements

Done,

Miguel Cobá
>
> Keith
>
>