Hey folks,
Thanks for the quick responses. Should have had gmane sort an "rtree"
query by date instead of relevance ...
On Sun, Oct 11, 2009 at 2:10 PM, George Hartzell wrote:
> Wow, there must be an outbreak of SQLite-genome-itis going around.
Apparently so! Perhaps it'll pop up on google's *
Igor Tandetnik writes:
> Steve Lianoglou wrote:
> > So I'm building a db with some RTree indices to store genome
> > information. Among other things, I have an RTree index to store the
> > start/end positions of genes on chromosomes. The problem is that the
> > numbers stored in the RTree aren
Steve Lianoglou wrote:
> So I'm building a db with some RTree indices to store genome
> information. Among other things, I have an RTree index to store the
> start/end positions of genes on chromosomes. The problem is that the
> numbers stored in the RTree aren't the ones I'm entering, sometimes
>
On Sun, Oct 11, 2009 at 11:29:02AM -0400, Steve Lianoglou scratched on the wall:
> This row should have start=94622317, why is it inserting 94622320?
>
> I know the rtree documentation says that the index "does not normally
> provide the exact answer," but I guess I'd be a bit surprised if this
>
Hi all,
So I'm building a db with some RTree indices to store genome
information. Among other things, I have an RTree index to store the
start/end positions of genes on chromosomes. The problem is that the
numbers stored in the RTree aren't the ones I'm entering, sometimes
they can be several base
5 matches
Mail list logo