> Storing +infinity, for example. It seems that in IEEE terms +infinity is
> different from NaN, but SQLite return NULL in both instances.
This is apparently some problem with your test setup.
SQLite version 3.7.5
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> create table t (n);
sqlite> insert into t values (1e305 * 1e305);
sqlite> insert into t values (-1e305 * 1e305);
sqlite> insert into t values (1/0);
sqlite> select n, typeof(n) from t;
Inf|real
-Inf|real
|null
sqlite>
Pavel
On Mon, Mar 26, 2012 at 10:37 AM, Francis J. Monari, Esquire
<monarifj....@juno.com> wrote:
> 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 North Sixth Street
> Camden, New Jersey 08102-1269
> 856-964-7759 (voice)
> 856-964-9620 (fax)
> mckernangod...@juno.com ("main", "office", "primary")
> monarifj....@juno.com
>
> Please use mckernangod...@juno.com as the ("main", "office", "primary")
> email.
> If possible please copy emails to monarifj....@juno.com.
>
> ATTENTION: This e-mail and the materials accompanying it convey and contain
> privileged and confidential information belonging to the sender which is
> legally privileged. The transmittal sheet, the materials, and the
> information they contain are intended only for the use of the individual(s)
> or entity(ies) named above. If you are not the intended recipient, you are
> hereby notified that any disclosure, copying, distribution, or any reliance
> on the e-mail, the materials accompanying it, or the information they
> contain is strictly prohibited, and that review by any individual other than
> the intended recipient shall not constitute waiver of the attorney/client
> privilege. If you have received the materials in error, please immediately
> notify us by telephone at 856-964-7759 or by reply email. We will arrange
> for the return of the materials to us. Please delete the copy of this
> message on your server. Very few methods of communication are 100% secure,
> please exercise appropriate care when using or replying to this message.
> Thank you.
>
> I.R.S. CIRCULAR 230 NOTICE: To comply with requirements imposed by the
> Internal Revenue Service (I.R.S.) please be informed that the advice
> contained in this communication was not intended or written to be used and
> cannot be used for the purpose of avoiding penalties that may be imposed by
> the I.R.S..
>
> McKernan, McKernan & Godino does not attempt to sweep e-mail and attachments
> for viruses. It does not guarantee that either are virus-free and accepts
> no liability or any damage sustained as a result of viruses.
>
> Jay A. Kreibich wrote:
>>
>> On Sun, Mar 25, 2012 at 02:03:44PM -0400, Francis J. Monari, Esquire
>> scratched on the wall:
>>>
>>> All,
>>>
>>> Not to sound critical, but to be clear: using SQLite for IEEE
>>> floating point will result in data "loss' unless precautions are
>>> taken.
>>
>>
>> Define "loss". SQLite, in general, is dependent on the underlying
>> hardware for floating point calculations. These calculations are done
>> within the limitations of the given hardware. Most modern hardware
>> is IEEE 754 compliant, but some mobile platforms are not fully
>> compliant. The SQLite application code takes great care in
>> converting between strings and IEEE 754 values so that no precision
>> or accuracy is lost.
>>
>> What other types of loss are of concern?
>>
>> -j
>>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
