I always find the db manager a little temperamental but overall I like using it and it works as long as I don't try to do too much at once. Anyway, I've now run into a breaking problem and I don't know if I can do anything or I just need to abandon using it for the project.
The problem is I have pushed a change successfully to the db but it keeps showing as a new change which then breaks future changes.
Specifically, I added a subtable - call it subtable A. It was added successfully and I can see it directly in the DB (connecting from outside Wappler). Wappler can see it and the change is logged and ticked as completed in the change history. Now I want to additional columns and add another subtable to this one. As soon as I click on subtableA in the db manager, it adds a dot and + signs (see image) as though it's a new change along with the badge to upload the changes.
If I click to upload it says "nothing to do". If I try to ignore it and proceed, any actual changes fail because "subtableA already exists". If I refresh (full schema or not) the badge disappears but comes back as soon as I click on the subtable.
Is there anything I can do? I'd prefer not to reset the change history if it can be avoided.
Thanks