Closed cielf closed 3 weeks ago
An alternate approach to fixing the current issues with fetch_latest_db As per suggestions from @dorner on #4388 -- see that PR for details of the issue. Approach from: https://stackoverflow.com/questions/2369744/rails-postgres-drop-error-database-is-being-accessed-by-other-users
This will just require that folks input their password, rather than having to run two different tasks to get to the final result.
Ran it after a cold boot. Then signed in and confirmed that the basic functionality works.
I'm good with this!
Description
An alternate approach to fixing the current issues with fetch_latest_db As per suggestions from @dorner on #4388 -- see that PR for details of the issue. Approach from: https://stackoverflow.com/questions/2369744/rails-postgres-drop-error-database-is-being-accessed-by-other-users
This will just require that folks input their password, rather than having to run two different tasks to get to the final result.
Type of change
How Has This Been Tested?
Ran it after a cold boot. Then signed in and confirmed that the basic functionality works.