======== TEMPLATE BUG FORM ========
Wappler Version : 5.4
Operating System : Windows 11
Server Model: NodeJS
Database Type:MySQL
Hosting Type:Docker
Expected behavior
What do you think should happen?
Database manager should update a change to a field.
Actual behavior
What actually happens?
Database Manager tries and reproduce the entire table and cannot since it already created the table. The database manager will show that there are changes for a table even though there are not. This happens after 2 or 3 commits not initially.
How to reproduce
- Detail a step by step guide to reproduce the issue
- A screenshot or short video indicating the problem
- A copy of your code would help. Include: JS, HTML.
- Test your steps on a clean page to see if you still have an issue
- Start and new NodeJS Project and Create and upload table to server using Database Manager.
- Create 2 more tables with an upload each time.
- Go attempt to change a field in the first table. Suddenly Wappler will show that there are changes pending, in this case 22 changes, even though the only change was to add a now() to an existing datetime field.
- Refresh the schema and lose changes. Now Wappler shows changed pending on table but no changes for upload.
- Make any change using the database manager now, like adding another column and it always says there are 22 extra changes to make. When it tries to apply the changes it produces and error saying it cant create the table, the first table ever created, because it already exists.
7, The only way to be able to make changes using the Database Manager is to roll back changes to before the first table creation, in my case 3 steps, and start over again.
Shows a a change is pending even though one is not.
Shows fields are new even though they are the first ones created on project.
Does not show pending changes until you simply highlight a field. Then it shows 22 pending changes.
The table with the changes is acually the intial table add. All the other updates went fine.
If you try and apply the changes you get this error, Table already exists.
Migration file with a create table for an existing table. The only update was the default now() was added.
Last updated: