23.03.2016 12:10, Alex Peshkoff wrote: > > isc_spb_utf8_filename is enough, see no need to have new version.
Please let's avoid choosing bad names. It has nothing to do with filenames. It should be something like isc_spb_utf8_data or isc_spb_utf8_strings instead. And yes, we need to add a properly named alias for isc_dpb_utf8_filename too. > Version is bumped when clumplets format is changed incompatibly (like > use of 32-bit clumplet length in new SPB version). Changing encoding > rules does not look like such change. I'd say the version can be bumped for any change that leads to wrong processing by the older code. Misinterpreted strings fit this rule. However, using *_utf8_* tags really looks like a hack in the long term. If we agree to move towards UTF8 in the long run, adding a new DPB/SPB version may be a good idea. Not necessarily in v4 though. Dmitry ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
