Hi, One problem with UUID (or any other randomly generated value) as the primary key is: when you have a lot of rows in the table (millions of rows, so that the data doesn't fit in memory), then accessing the data by this key is slow, because the data is randomly distributed over the disk. Regular disks have a high seek time, so this will be a problem.
As an example, this is a problem with Apache Jackrabbit (which uses UUIDs as the internal node ids) if the repository is large. It's not so much a problem if you are using solid state disks however. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
