Attached is the EncodedStream class from AmorphousDB as an example of what
I've been talking about. The module has types that Firebird doesn't need
and is certainly missing types that Firebird needs, but it demonstrates
what I've been talking about. Please note that it has not been licensed as
op
On Mon, Mar 2, 2015 at 8:35 PM, Slavomir Skopalik
wrote:
> Hi all,
> after discusion with Jim, I was created frist draft of proposal for
> value encoding.
>
>
>
> Any comments?
>
>
[Second attempt; first bounced because of size]
Attached is the EncodedStream class from AmorphousDB as an example
You missed the point. You can do much, much better.
Use the full range of codes. Don't split the code byte into code + value..
Give yourself the full 256 code space.
Have a range of values to specific numbers and one byte ints, two byte ints, up
to eight byte ints.
Have a set of codes for s
Hi all,
after discusion with Jim, I was created frist draft of proposal for
value encoding.
Pros: efectivity for numerical values including date and time
Cons: poor for strings (can be worst then current), can be solved by
apply RLE (not current) over final result.
It is designed as simple (the
