[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ordered indexing for integers

Quanah Gibson-Mount wrote:
> --On Tuesday, November 20, 2007 6:57 AM -0800 Howard Chu <hyc@symas.com>
> wrote:
>> I was looking at adding support for ordered indexing for Integer
>> attributes. This would be an incompatible format change for index
>> databases. In fact I'd need to change the Presence index key as well, so
>> it would affect all index databases, not just those for Integer
>> attributes.
>> Currently the Presence index uses a hardcoded 4 byte key of 0x00000001. I
>> want to change it to a 2 byte key of 0x0000 instead, to prevent it from
>> colliding with the Integer key space.
>> So far, 2.4 and 2.3 have totally identical database formats. Is it
>> worthwhile to break this compatibility to gain this feature, or better to
>> preserve compatibility and ignore this feature for now? Any thoughts on
>> going ahead with it here in RE24?
> I think every other release has had incompatible changes, and if we are
> contemplating one for 2.4, we need to do it sooner rather than later.
> Since 2.3.39 was just marked stable, I'm guessing not too many people
> have migrated to 2.4.6 so far.  We'd definitely want to note highlight
> this change when pushing 2.4.7.  As for the feature, I think it sounds
> quite useful, I've wanted to do ordered integer searches in the past...

I agree this feature could be very useful and at this time 2.4 should be
early enough in its life to undergo this change.  Otherwise, we'd have
to move to 2.5 without dramatic improvements but an incompatible
database format change.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Email:   pierangelo.masarati@sys-net.it