I'm going to read it later, but, I'll be going in skeptical. Collision is real, even at 128-bit resolution, but if your code handles the potential of such a thing, then its no different than an autoinc primary key. I'm rather interested in their reasoning.
On Thu, Nov 30, 2017 at 9:15 AM, Simon Slavin <slav...@bigfraud.org> wrote: > Thought some of you might enjoy seeing this article. I make no comment on > what I think of the reasoning therein. It’s set in the PostgreSQL world, > but you could make an external function for SQLite which generates UUIDs. > > <https://www.clever-cloud.com/blog/engineering/2015/05/20/ > why-auto-increment-is-a-terrible-idea/> > > "Today, I'll talk about why we stopped using serial integers for our > primary keys, and why we're now extensively using Universally Unique IDs > (or UUIDs) almost everywhere." > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
