l 2012 17:52
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] rtree value rounding
>
> On Tue, Apr 24, 2012 at 11:41 AM, Jos Groot Lipman
> <donts...@home.nl> wrote:
>
> > The next version of Sqlite will very likely support 64 bit
> integer
On Mon, Apr 23, 2012 at 06:36:35PM +0100, Shish scratched on the wall:
> The rtree docs say that as well as 2D geometry, it could be used to
> index ranges of time - this is what I'm doing, but I've found a
> problem and workaround:
I think you're missing the idea of R-Trees. I would suggest
sqlite.org] On Behalf Of Shish
> > Sent: maandag 23 april 2012 19:37
> > To: sqlite-users@sqlite.org
> > Subject: [sqlite] rtree value rounding
> >
> > The rtree docs say that as well as 2D geometry, it could be
> > used to index ranges of time - t
qlite.org] On Behalf Of Shish
> Sent: maandag 23 april 2012 19:37
> To: sqlite-users@sqlite.org
> Subject: [sqlite] rtree value rounding
>
> The rtree docs say that as well as 2D geometry, it could be
> used to index ranges of time - this is what I'm doing, but
> I've
Shish writes:
> The rtree docs say that as well as 2D geometry, it could be used to
> index ranges of time - this is what I'm doing, but I've found a
> problem and workaround:
>
> It seems that the indexed values are stored as a small floating-point
> value, and thus large numbers (for
The rtree docs say that as well as 2D geometry, it could be used to
index ranges of time - this is what I'm doing, but I've found a
problem and workaround:
It seems that the indexed values are stored as a small floating-point
value, and thus large numbers (for example, the current timestamp as
6 matches
Mail list logo
