On Wed, 12 Jun 2019 12:57:22 -0400 Richard Hipp <d...@sqlite.org> wrote:
> On 6/12/19, Thomas Kurz <sqlite.2...@t-net.ruhr> wrote: > >> For an SQL engine, the next-best-thing to strict binary IEEE754 is > >> not > > sloppy binary IEEE754, its probably strict decimal IEEE754. > > > > That would be a *really great* improvement! > > It would also be a file format change, rendering about 1e12 existing > database files obsolete. Is that necessarily the case? Could blob types be "overloaded" somehow, such that existing code sees a blob and new code recognizes said blob as decimal numeric? For example, if the first two bytes of the expansion area of the database header (at offset 72) were 0x0bcd (say), then record type 44 could represent a 128-bit decimal encoding [16 bytes = (44 -12)/2]. Existing programs wouldn't examine the expansion area, and would interpret the field as a blob. New programs would interpret type 44 as decimal or blob, depending on the CREATE TABLE definition. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
