Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Won't Fix
-
Affects Version/s: 4.2.0
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Hi,
Testing the upgrade process, it's likely the start db was in bad shape, because I got error messages.
On the old upgrade, I got errors that where useful (exactly what command was in error), so we could manually fix/inspect)
Now, we only have 'No such field' and that's it, don't know which field or the table, don't know how to debug.
Would save a lot of problems to display back the complete sql in error