Re: [sqlite] NaN in, 0.0 out?

All, Storing +infinity, for example. It seems that in IEEE terms +infinity is different from NaN, but SQLite return NULL in both instances. Is there a standard "SQLite" style of handling this situation? Frank. Francis J. Monari, Esquire McKernan, McKernan & Godino 113 Nort

Re: [sqlite] NaN in, 0.0 out?

All, Not to sound critical, but to be clear: using SQLite for IEEE floating point will result in data "loss' unless precautions are taken. Assuming my statement above is correct, then does a standard set of precautions exist? Frank. Francis J. Monari, Esquire McKernan, McKernan &am

Re: [sqlite] NaN in, 0.0 out?

All, How are +infinity and -infinity handled? Frank. Simon Slavin wrote: On 25 Mar 2012, at 3:48am, "Jay A. Kreibich" wrote: On Sat, Mar 24, 2012 at 07:32:32AM -0400, Richard Hipp scratched on the wall: SQLite converts NaN inputs into NULL. I think this is the right

[sqlite] numbers in nvarchar fields (text? affinity)

list, I experienced the following situation: * field holding a file identifier (currently only numbers). * the field type is nvarchar (text? affinity). * some file identifiers have leading zeros. * of those file identifiers having leading zeros, some leading zeros are being stripped off (handled