======== TEMPLATE BUG FORM ========
Wappler Version : 3.5.5
Operating System : Mac
Server Model: Node
Database Type: MySql
Hosting Type: Docker Local, AWS remote.
What do you think should happen?
Trying to pull from GIT. Should happen as expected.
What actually happens?
This error:
I believe it might be due to a > in the filename. But if I remove the file/update the name then the DB Manager changes become corrupt. Any ideas team?
Hey @George any workarounds for this without losing the DB changes history
This might not be ideal because it involves downloading and saving then uploading, but you could try the Save Database Data and Structure option.
Thanks @scott - tryng to avoid this as I want to hold the DB changes in full in the DB Manager for when we move to a full prod DB.
Any ideas @George?
Did you name your change description with > in it?
Seems we have to do some clean up as those shoun’t be allowed indeed.
As for your resolution well you should check it out on a system that allows it (or the original check in) - rename it and then commit back.
I did name it with an > which I won’t again.
I’ll try and get your suggestion working. Thanks!
@George so looking at this, and I remember trying to change the name previously.
The issue is, it’s actually the name of the change file that’s got the > within it and causing the issue. There is no ‘rename’ option in Wappler for the name of the change, for me to change and then re-commit. If I change the name directly in the migrations folder then it just corrupts the staging/prod changes environment.
Any other suggestions?
@George any further guidance on this?
