On Wed, Jun 27, 2012 at 1:12 PM, Doug Currie <[email protected]> wrote:
> On Jun 27, 2012, at 10:41 AM, Richard Hipp wrote: > > > This is a work in progress. > > The SQLite4 numeric format sounds like a great improvement; on the doc > page you say: > > > The SQLite4 numeric format is for internal use. Numbers can be > translated between integers or doubles for input and output. > > Presumably SQLite4 numbers may also be translated from/to text without > going through integers or doubles? This would avoid all the issues with > "why does 1 / 10 != 0.1?" we see on the mailing list. > That's the idea. Of course, at the moment, it is mostly theoretical, as the current implementation still uses "double". Routines to work around that have been written and tested (a little) but have not been integrated. The important point is that the file format is consistent with decimal numbers. As long as the file format doesn't change, we can switch around the implementation as much as we want (perhaps using decimal64, for example). > > e > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
