Something did change. Previously, weewx used transaction isolation level "READ UNCOMMITTED." Now it uses "READ COMMITTED."
But, according to the error message in your first post, both are limited to row-based logging, so I don't know why this change would suddenly cause the error. -tk On Sun, Mar 12, 2017 at 10:23 PM, Craig Thom <craigt...@gmail.com> wrote: > Yes, I was using MySQL, and I changed nothing in MySQL. The only thing I > changed was upgrading weewx. The MySQL server is on the same machine as > weewx. > > I got it working, but it did require a change to my MySQL configuration, > the configuration that was working fine before the weewx upgrade. So > something in weewx changed. > > > On Sunday, March 12, 2017 at 11:44:57 PM UTC-4, mwall wrote: >> >> craig, >> >> were you using mysql before you upgraded to weewx 3.7.0? >> >> is the mysql server on the same computer as weewx? >> >> m >> > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to weewx-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
