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
Now I've updated another local site, and both of these sites' live instances, + they updated with no problem :-) and the original update with the error is problem free. This certainly is rare,...
1.23.1 update results in: Call to undefined function file_needs_type_classification()
I didn't know about the mail.css. That will be useful. I also wanted to be able to get notified by new content types, not just comments. I believe I can only get this with notity. Isn't?
notifications with html mail
node_notify does send html emails and doesn't require notify. Do you need also the notify module? As for formatting, mimemail will use the mail.css file located in your theme's css folder. I would...
notifications with html mail