Edited wiki page OutstandingTopics through web user interface.

OutstandingTopics.wiki

diff --git a/OutstandingTopics.wiki b/OutstandingTopics.wiki
index 69f359b..196179f 100644
--- a/OutstandingTopics.wiki
+++ b/OutstandingTopics.wiki
@@ -25,8 +25,7 @@
 For Jdbc dialects the methods: `beginTransaction()`, `commit()` and `rollback()` are no-ops:
 `java.sql.Connection` is opened in `autoCommit=true` mode, which means that all executed
 statements are immediately committed. This obviously cannot work with optimistic database locking strategy that `GWTORM` is using, because it is expected with this approach that some statements
-can and would fail with stale row manipulation error. But this means a disaster with not proper working transaction management, because previous statements were already committed,
-leaving the changes in undefined state. The consequences are all these reported issues [https://code.google.com/p/gerrit/issues/detail?id=2034 1], [https://code.google.com/p/gerrit/issues/detail?id=2246 2], [https://code.google.com/p/gerrit/issues/detail?id=2383 3], [https://code.google.com/p/gerrit/issues/detail?id=2702 4],
+can and would fail with stale row manipulation error. But this means a disaster with not proper working transaction management, because previous statements were already committed, leaving the changes in undefined state. Note: all databases supported by Gerrit have transaction support (with one exception: MySQL's MyISAM storage engine). The consequences are all these reported issues [https://code.google.com/p/gerrit/issues/detail?id=2034 1], [https://code.google.com/p/gerrit/issues/detail?id=2246 2], [https://code.google.com/p/gerrit/issues/detail?id=2383 3], [https://code.google.com/p/gerrit/issues/detail?id=2702 4],
 [https://groups.google.com/d/topic/repo-discuss/KUUBaI29QO8 5].
 
  * Gerrit changes: [https://gerrit-review.googlesource.com/57860 change]