-=| Alex, 13.12.2013 09:01:12 +0400 |=- > On 12/13/2013 01:14 AM, Damyan Ivanov wrote: > > > On a related note, I wonder if there is a way to convince firebird to > > work with collations created with different (and no longer available) > > version of ICU. This would minimise the efforts when upgrading ICU. > > With no longer available version of ICU - no. How can one work with > missing software?
I called it a hack on purpose :) Current patch is at http://anonscm.debian.org/gitweb/?p=pkg-firebird/2.5.git;a=blob;f=debian/patches/ignore-collation-version.patch It ignores any collation version mismatches, replacing "COLLATION UNICODE_CI for CHARACTER SET UTF8 is not installed" error with a warning in the log ("Ignoring collation version mismatch. Wanted 58.0.6.48 but will try to work with 58.0.6.50"). This gives me the freedom to decouple ICU upgrade from database backup+restore, at the expense of possible incorrect searches if the collation of the used characters has changed. I realize this is not suitable for inclusion upstream, as it is too intrusive, replacing "give version X" with "give first available version". Perhaps it should fall back to the first available version only after examining all available ICU versions and/or if allowed via a configuration option. > We had a plan to add something like > RECREATE INTL INDICES > command, but it's not ready yet. This sounds like an excellent idea! -- dam ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
