On Fri, Jun 29, 2012 at 5:58 PM, Richard Hipp <d...@sqlite.org> wrote: > > On Fri, Jun 29, 2012 at 6:40 PM, Nico Williams <n...@cryptonector.com>wrote: > > > On Fri, Jun 29, 2012 at 5:24 PM, Richard Hipp <d...@sqlite.org> wrote: > > > varint+value does not sort BLOBs in lexicographical order. > > > > > > Not having a distinct terminator for the BLOB means that two BLOBs where > > > one is a prefix of the other might not compare correctly. > > > > Would 31-bit encoding help? > > > > Maybe. > > But you know: How often do people use BLOBs as keys? What other SQL > engines other than SQLite even allow BLOBs as keys? Are we trying to > optimize something that is never actually used? >
128-bit GUIDs as a primary key are very common in cases where records are to be synced between two (often disconnected) databases. Admittedly 3 bytes of overhead in this case is probably not going to be a huge deal, but if a 19% overhead can be avoided early in the design, why not? Okay. I'm done bike shedding ;) -- Cory Nelson http://int64.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
