It's basically a non-problem.
In 20 years of database programming, I've never seen it myself.
For people who did see it, the recommended approach was to lock the data
by hand for the relevant queries, using LOCK TABLE or FOR UPDATE clauses.
On 2013-05-18 01:58, 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.
