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
I'm not sure I'm getting it. It is working as intended now. Let me post you some images. Thanks!
have a view show contents in table and leaflet format simultaneously.
https://github.com/backdrop/backdrop-issues/issues/7018 Feel free to edit as you see fit. KR Mike
MySQL Database 4-byte UTF-8 support
Thanks. Would you please file an issue at https://github.com/backdrop/backdrop-issues/issues? The idea there is to say that a site that uses a DB prefix defined in the simplified database...
MySQL Database 4-byte UTF-8 support