Well you could get a global database lock with every transaction, it
would kill concurrency, but you'd be ensured to never get a deadlock :P
Sorry, not very helpful :), but no-one else has replied on here :)
On 18/05/2013 7:58 AM, Gili wrote:
Hi,
I wanted to get your opinion
regarding http://stackoverflow.com/a/112256/14731
Is it fair to say that database deadlocks are not preventable:
1. Using portable SQL, since the SQL standard does not specify lock
ordering;
2. Using database-specific SQL code, because the execution plan of a
database might change over time.
Thank you,
Gili
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
