Hello Simon,
>This has the advantage of removing the chance of a name-space collision. That's true as well: it is an added free bonus. But honestly I would say that for such transient usage a random generated name is fairly unlikely to cause real-world problem. select hex(randomblob(16)); just gave "in a row": 207FA9389DDD09302E61D45E08571BD7 D8D15A725C34263099BCC95373596214 7458A094F3EF6673A7ADADFBF0F54EB3 I doubt somebody would be able to come up with a collision easily. Even if a collision is utterly unlikely but still possible, I wouldn't worry that much for transient table names or transaction ID having only few seconds lifespan. And NO, I don't open here the GUID can of worms for _permanent_ IDs, which is a very different story... _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
