On 27/03/2011, at 3:04 PM, Patrick Earl wrote: > If you use a view to return a double, you've lost the exact value you were > trying to save by storing the decimal as a text value.
I'm not suggesting storing as a text value. I'm suggesting storing as an integer and only converting to a float (or, I guess a text value is possible too) for display purposes. > If you continue to work with it as an integer, it's exact, but that requires > continual awareness of the number of decimal places at any point in time. If we're talking about money amounts, isn't the number of decimal places always two? ie an amount stored as an integer as 12345 means 12345 cents means 123.45 dollars. > In essence, you have to build significant numeric infrastructure into your > program to emulate the missing numeric infrastructure in SQLite. Perhaps I'm missing something of your requirement. I use integer storage for exact lossless money amounts. Tom BareFeetWare -- iPhone/iPad/iPod and Mac software development, specialising in databases develo...@barefeetware.com -- Comparison of SQLite GUI tools: http://www.barefeetware.com/sqlite/compare/?ml _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
