2012/3/7 Thomas Mueller <[email protected]>: > This is not a bug in H2. The problem is that you used "WHERE > <condition>" instead of "ON <joinCondition>". H2 supports the omission > of an "ON" condition, and uses "ON 1=1" in this case.
Okay, my SQL was wrong. I'll amend it when I am back. Thanks. > Please note that using randomly generated UUIDs as the primary key > will result on poor performance once there are millions of rows in a > table. The reason is that the cache behavior is very bad with randomly > distributed data. This is a problem for any database system. In this case it will not be a problem, because I will not have this amount of records, but it is good to know. I am not a database expert, but I thought that with hash-tables you should not have this problem. That is not the case? The reason to use them is that it is easier to merge databases. (The 'same' application will run on one or more pc's and one or more mobiles. In this way the data can be merged. Or is there a better way for that?) The other question I could better repost in another thread. ;-} -- Cecil Westerhof -- 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.
