Michael Ströder wrote:
Howard Chu wrote:
>> If incompatibility worries people even as early as this in 2.4's life,
>> we could leave the old format as the default in 2.4, and provide a
>> slapd.conf-option to enable ordered indexing.
> OK, I guess we can add a config option to switch formats.
For how long will this database backward compability be guaranteed? Will
this config switch affect other changes in database format? Don't open
this can of worms...
Nothing else is affected, just the Equality index for Integer attributes.
Since others also agreed that 2.4.7 is still early enough I'd
avoid another config option. But 2.4.7 should released during next two
weeks for introducing this change early enough.
We can make it the default and remove the config option. I'm fine either way.
Currently the default is still the old hash format, but it's easy enough to
remove the option.
IIRC in some former days database format changed frequently even
a media release series (don't remember which one). IMO migration from
2.3.x to 2.4.7+ is a significant update with lots of changes.
slapcat/slapadd seems a reasonable migration action anyway.
Well, from 2.3 to 2.4 a change wouldn't be very surprising. This is 2.4.6 to
2.4.7, which may be more surprising.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/