> > As a result, I don't think it's wise to use them, objectively speaking. It has > very little to do with having used them in the past myself or not (OT: that is > actually a psychological trap employed by many shady business models ;) ). > I do hope that if you use them, you never run into collisions and having to > sort out the pieces afterwards. >
I have done a fair amount of research here as it is connected to a project I am involved in. The only real advantage of UUID is for distributed creation of records. The disadvantage of a sequence is that a single mechanism, that supplies the PK, needs to be accessed and locked whenever any record anywhere is created. This is an issue for distributed databases (what I am involved in), but not an issue for an sqlite one, which almost by definition, is not distributed. If you are using sqlite as a distributed database, the first question must be "why?", and the second reaction should be "you should be designing the application accordingly then", such as generating the UUID yourself rather than sqlite do it. In short, it would be incorrect for sqlite to move over to UUIDs as the standard PK mechanism. Eddy
