The order for RTREEs is min_dimension1,max_dimension1,min_dimension2,max_dimension2...
51.51340259 is definitely greater than -1.86352760 Best regards, Peter ________________________________ From: "g...@novadsp.com" <g...@novadsp.com> To: sqlite-users@sqlite.org Sent: Wed, January 18, 2012 11:51:41 AM Subject: Re: [sqlite] R*Tree insert error ... On 18/01/2012 18:04, Dan Kennedy wrote: > One possibility is that you're hitting one of the r-tree tables > built-in constraints by specifying a record with (minval > maxval) > for one or more of the dimensions. Rearranging the bind parameters for match minx,miny,maxx,maxy layout I now get this (doubles dumped with 8 decimal places) Inserting ID: 01, 51.51340259, -1.86352760, 51.51340259, -1.86352760 failure at read() error code 19 (constraint failed) This is repeatable using Sqlite3 sqlite> INSERT INTO gps_index VALUES(01, 51.51340259, -1.86352760, 51.51340259, -1.86352760); Error: constraint failed sqlite> > (minval > maxval) So how does one insert a point? Is there a magic fudge factor involved? Surely minval >= maxval? I cannot see anything at http://www.sqlite.org/rtree.html Help much appreciated. Thanks. Jerry _______________________________________________ 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
