The more I think about it, the proposed unified numeric model makes
a lot of sense and should be the default with no pragmas or compile-time
options for the old behavior. The dynamic manifest typing model of Sqlite
practically begs to have uniform mathematical results given the
dynamic nature of the operands:
SQLite version 3.2.7
Enter ".help" for instructions
sqlite> create table foo(a);
sqlite> insert into foo values(7);
sqlite> insert into foo values(7.0);
sqlite> select a/6 from foo;
1
1.16666666666667
If the columns of tables in Sqlite would strictly enforce types -
this would be a different matter. But since they do not (and will not),
the proposed behavior is more logically self-consistent.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
