> If it should do division the same way for every operation then you must > require the result to be able to represent every possible division > result. IE the result must be floating point. If you're writing the inner > loop for a quake engine there are very good reasons for not wanting to pay
I'm not writing a quake look in SQL. No one with any sense would. All this change does is make SQLite even more data type agnostic than it was in the previous version. > floating point operations. If you're creating a very large database why should > you pay for 80 bits (an IEEE float) of storage when 8 will do just fine? So don't make the field 10 bytes long, make it only 8. SQLite won't care a bit, and will give you the value in whatever format you want. Brad
