Closed lmajano closed 3 years ago
And also some kind of indication of which migration file failed in the case of SQL errors. A simple dump of the filename while spooling through the migrations would work. As an example, which of the 6 migrations that needed to run here failed? https://www.screencast.com/t/ATWzEPeeTx0I
@lmajano To get the full exception information, use --verbose
@Daemach That is a good suggestion. I'll add a new ticket for it.
As it stands, the errors when having connection issues are not nice.
Nothing more nothing less. Looks like a hibernate error :(
We need to improve these error messages and show WHY we could not connect.