Evergreen

  1. Bug #1768869
  2. Comment #3

Comment 3 for bug 1768869

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

Mike, that sounds like a great solution. I added that command "select auditor.update_auditors();" to the end of a test db upgrade and it fixed the problem.

What would be a good way to get this included in the next version upgrade scripts for 3.1 and 3.2? I'm not familiar with how the version upgrade sql files get created. If there are a set of instructions for creating those, them maybe that just needs to be updated? Is there a script that builds the version upgrade from the upgrade/xxx*.sql files?

Thanks
Josh