Message of the day:
SS 4.4.0-RC1 is out. Changelog: https://github.com/silverstripe/silverstripe-framework/blob/4.4/docs/en/04_Changelogs/4.4.0.md
SilverStripe 4 related information and questions.
In saying that, building the database from the same code base but in a staging environment on CentOS didn't encounter the naming issue so my guess is that it's Windows specific.
Also, try run
deb/build again. One time it would throw an error on each table it was trying to update the name on, then the subsequent build, it would get past that table, then throw an error on the next 'version' table in line. Repeated process as many times as there were 'version' tables and it didn't throw the error again.
@mmativ I've had a similar issue when working in Ubuntu machine via Vagrant as a guest box on a Windows 10 machine. For me, it was that SiteTree_Versions and SiteTree_versions weren't treated as case sensitive so attempted to rename and change the lower case v to an upper case V was the issue. If you can manually change the name via what ever tool you use to access the database, that could fix it.
Maybe server log will give more details?
I experience that before on my local, i just republished all pages that have the error but how can i re published the SiteTree
yeah 😅, because there’s no other details on the error
the line after that will be the error, not the line before :)