On 23/02/2015 16:36, James Starkey wrote: > Encode null as a value type and skip the null flags altogether -- > saves a couple of bytes for every record. > > I'd encode the format version as the first value. That will let you > have 2^63 format versions, which should be enough. > > I'd getvthe transaction id in the record header rather than the record > itself so it can be compared (a high frequency operation) with decoding. > > And yes, encoding is based on actual value, not declared type. This > opens up some interest possibilty such as abstract "number" and > "string" types without declared length. Did that in NuoDB. Ain't > SQL, but very usefull. > > What sort algorithm you use to order strings with length varying from 1 to millions of chars?
Adriano ------------------------------------------------------------------------------ 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=190641631&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
