Upgrade to 1.40.0.7998 causes error

Pong! :rofl:

Regarding these new errors showing up with the DB…

  1. There are a LOT of broken databases out there which nobody knows about

  2. PMS 1.40.x, with its new DB structure is exposing those errors

  3. Some of the errors are insignificant while others aren’t.
    – “No such column” comes from another error having prevented updating the DB correctly in the past so now there are two errors in one.

  4. Given any errors represent data missing. we need to figure out how to get over the error and (re)create what’s missing.

If we can figure out a process, we’ll hopefully be able to save folks from doing a full-rebuild of the DB