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
This has always been available using a separate module. Now added to the core, thanks for developers.
Gallery inside post content
It's the reason why i refuse "builder" because finally, you have a "student blog". But a gallery it's not a crazy thinks. All CMS propose it. Too many constraints can also scare your...
Gallery inside post content
There is such a thing as a "publication format" — all publications must be made in the same style, which was developed by the designer, and the task of the editor is to fill in the provided...
Gallery inside post content