On Wed, Apr 23, 2014 at 6:56 AM, Keith Medcalf <kmedc...@dessus.com> wrote:
> You don't ever really need a GUID at all. Simply use an "integer primary > key" (an integer starting at 1) and simply pretend that it is being added > to the applicable base GUID of your random choosing. Everything will still > be unique and you will have saved yourself a crap load of storage space, > index space, and conserved countless CPU cycles so that they can be spent > on something more productive productive. > > I have never seen a need to actually use a GUID for anything, it is a > ridiculous concept. > Until one implements a DCVS (i.e. Fossil), at which point sequential numbers become literally impossible to generate. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
