11.12.2014 15:32, Alex Peshkoff wrote: > I've almost finished with SQL command fixing database to make it usable > with ICU version not matching one with which database was created. This > helps in a cases like one described in > http://tracker.firebirdsql.org/browse/CORE-4571 . With mentioned > improvement one will be able to issue special SQL command which > redefines collations information and recreates required indexes to make > them use keys generated by current ICU library. > > "Almost" means that everything works as expected but I have no idea what > name to give to this non-standard SQL operator. And I want to know your > mind about it.
Does user need to know what is the "current" ICU? Or "current" would mean the one that can be found? What to do if multiple ICU versions are installed and accessible? So far my thoughts are walking around: ALTER DATABASE USE ICU [VERSION] <string> or ALTER DATABASE RESET ICU TO [VERSION] <string> Dmitry ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
