If a watchdog entry should be written during a different MySQL table is locked it will fail with MySQL error "Table 'watchdog' was not locked with LOCK TABLES". If a watchdog entry should be written during an open transaction and the transaction will be rolled back, the watchdog entry will be removed as well. Both cases could be avoided if we use a dedicated database connection for writing watchdog entries.
The solution is to declare a dedicated database connection which will not be established until required.
If a watchdog entry is written as part of a transaction it should probably be rolled back with that transaction. But for entries of severity WATCHDOG_ERROR or above we should assume that they should be always written. But his behavior has to be optionally configurable in settings.php.
Original issue: https://drupal.org/node/298768
Recent comments
You can use Rules or the Node Notify module for comments. When a new account is created, I believe there are Rules to send.
Email notifications
There's a few way to accomplish it, but it really depends on your full requirements. I'm working on a contact management module but it won't be released for a few months. There...
Pairing fields
I'm fairly sure that some people have done this successfully in Backdrop. Please can you list the modules you are using; that should help us get the right people to join this conversation.
How to render facet blocks?