On 11/2/05, Brass Tilde <[EMAIL PROTECTED]> wrote: > > > 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. > > > Then it's not type agnostic any more. You now have an 8 byte numeric > > and a 10 byte numeric. Which is no different than integer and real. > > From SQLite's standpoint it is agnostic. SQLite neither knows nor cares > what is actually stored in the column; that's up to your application to > deal with. Whether those 8 bytes represent a generic number, a real > value, an integer, a floating point value, date or text is for your > application to determine, not the DB engine. At least from SQLite's > perspective.
The only way for this to work will be to remove all mathematic operations. You can't make it agnostic of types if you have more than one type and allow operations to be performed on the types.
