-=| Alex, 13.12.2013 16:49:35 +0400 |=- > Your patch with great success causes first one - data may be > _silently_ (people useally do not read logs) lost when not found in > index. Performing backup without ICU version upgrade is already > possible, and letting people do some more things is making very bad > thing for them.
I see what you mean, and I admit I may be too patch-happy here. In my defence I'll point out that I thought that I am forced with a day-long backup+restore cycle (× multiple databases). As it turns out, this is not the case. On the bright side, I've learnt more about the ways Firebird uses ICU collations, so here's the recipe for recovering after "collation not installed" error after upgrading Firebird/ICU. In fbintl.conf, add your previous ICU version (4.8) to the list of icu_versions, after "default" and keep libicu48 package installed (my earlier statement that you can't have different icu versions installed at the same time was wrong). The result is that collation error is gone and you are free to do the backup+restore when convenient. For all this to work, the ICU loading code has to support both 4.8-style and 52-style library filenames, which I borrowed from the implementation in trunk. The end result is at http://anonscm.debian.org/gitweb/?p=pkg-firebird/2.5.git;a=blob;f=debian/patches/out/icu-version.patch Thank you for your help, and sorry for being too eager to patch. -- 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
