Often times people will use GUIDs as primary keys when different systems need to generate rows and then merge together. Like an application that works with offline clients that push the data to a server when the connect. However there are other ways of accomplishing the same thing.
Sent from my iPhone > On May 20, 2015, at 3:50 PM, Mark Straver <sqlite-users-list at palemoon.org> > wrote: > > Just to chime in here: I think using UUIDs for primary keys is an absolutely > terrible idea, instead. First off, how are you going to generate them? How > will you avoid collisions? Why should it be necessary to using that much > storage space for a primary key and what's the reason for not using > blazingly-fast integers?... > >> This is very unusual but, I think, contributes a lot to how portable SQLite >> is: no need to understand folder structure or safe places to keep >> configuration information; increased startup-speed; reduced code size, fewer >> file handles, slightly reduced memory. > > I think the fact that it's called "SQLite" is for a reason ;) > > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
