Comment 3 for bug 1641609

Revision history for this message
Alexei Sheplyakov (asheplyakov) wrote :

> And for new deployments, one can always drop the existing schema completely (as it's empty - there no rows in tables yet) and re-create if from scratch by the means of migration scripts.

this requires manual intervention and is not acceptable.
(Leaving aside that it's next to impossible to find out that failed due to db sync error due to overly generic Fuel's error messages)