On 2013-02-27 10:19, Ryan How wrote:
This doesn't really help, but I thought the idea of MVCC is to be an optimistic lock?. So by definition it shouldn't be able to timeout as it doesn't even need to get a "lock" ? Or am I grossly misunderstanding something here? Does "FOR UPDATE" still lock a table for other "writers", it just doesn't lock it for other "readers" ?
Try reading about MVCC first. http://en.wikipedia.org/wiki/Multiversion_concurrency_control -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
