Re: [Firebird-devel] Planning the post v3 development

[Jim S. <ji...@ji...>]

On 4/24/2014 6:19 AM, Dmitry Yemanov wrote:
> All,
>
> We're getting closer to the v3.0 feature freeze which is going to happen
> this summer. Everything roadmapped for v3 but not implemented before the
> deadline will be postponed. The next-after-v3 release is likely to
> incorporate most of the postponed features, but there may be new
> features as well. So it makes sense to start discussing what could and
> should be done in the next version(s). We have a few months to collect
> the proposals, discuss technical details and make estimates about the
> required efforts.
>
>
I suggest you consider the following:

 1. Switch internals to UTF-8 only.  Let the client handle mappings
    between national character sets onf UTF-8.
 2. Switch to an encoding based on actual value rather than declared
    value to achieve a packing density 30% less than run length encoding
    and to support strings of unbounded length and over-specified
    numeric types.  It might be necessary to extend the API to support
    unbounded string.  This would have a side effect of allowing 127
    character object names as per the standard.
 3. Implement schemas to support a two level name space.
 4.