On Jul 12, 2008, at 11:08 AM, Dan wrote: > > On Jul 12, 2008, at 2:42 AM, Steve Friedman wrote: > >> >> >> Filip Navara wrote: >>> how about actually attaching the patch? :) >>> >>> - Filip >>> >>> On Fri, Jul 11, 2008 at 9:23 PM, Steve Friedman >>> <[EMAIL PROTECTED]> wrote: >>>> I've just started using the rtree extension, and have found that >>>> the 32-bit >>>> float for the range keys is not appropriate for me. Please find >>>> attached a >>>> patch for rtree.c (based on v1.5) that allows for int -OR- >>>> unsigned int -OR- >>>> float operation. > > What kind of advantages does using int over float have here? > > With a little work it might be possible to select int or float at > runtime. Do other people who know about such things think that this > would be a good option to have? >
An important class of problems use all 32bits of an integer. Simply don't have enough bits in a 32bit float to cover integer range. Perhaps the implementation just looks at the type supplied on the create table statement. To keep things simple throw an error of they are not all the same type or are of an unsupported type. Unsigned ints should be supported! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
