> Please read the recent thread "What is quicker" which has a long
> discussion on the limitations of floating point.
>
> A short summary might be, "Unless you assume that any value stored in
> floating point format is only an approximation to the input value, you
> will run into trouble sooner or later." If you need exact results (and
> want to avoid a _lot_ of analysis), use string values or integers
> (possibly scaled).

I can create table as

CREATE TABLE photo_tags
(
  save_date REAL collate binary,
...
);

and compare is right, but is this correct way for date values?

> Also, when starting a new thread, please do not just reply to an ongoing
> one and change the subject.

I'm sorry.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to