On Tue, 17 Jan 2012 11:35:58 +0000, "g...@novadsp.com" <g...@novadsp.com> wrote:
>Thanks Simon, > >> Neither of those things are simple. >> >> Rather than hack an existing library, I recommend that you allow the R*Tree >> module to maintain its integer keys and make another (normal, not R*Tree) >> table in the same SQLite database to keep the list of GUIDs vs. integer keys. > >Ouch :) If the GUID can be represented as a 64 bit signed integer you can use it as the INTEGER PRIMARY KEY of the RTree table by itself. "Real" GUIDs are 128 bit though, so it will only work if you have a static prefix or suffix part of sufficiently large size that you don't have to store in each and every row. -- Regards, Kees Nuyt _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
