I think that applying DB changes is not completely obvious now. Let me explain.
Suppose I have two targets: local and prod. Both of them connected to different external databases.
I wanna make changes in schema for both DBs through Wappler.
The plan is to add new fields locally and then apply them in the prod.
Current steps in local target:
- In Database Manager go to an already created table and add a new field. You clearly see it appeared in the list of the fields.
2. Press “Apply Database Changes”, enter some description.
3. Suppose you change target and then change it back (doesn’t matter why, you just want to do that)
4. Go to DB Manager and open the table again. You can’t see the new field you created before.
This happened because you don’t refresh the schema manually. But you didn’t know that you needed to do it!
5. You click “Refresh schema” in the context menu and now you are ok.
After that I go to prod in order to apply changes there.
- Change target
- In DB Manager go to Changes and apply them.
- You still don’t see changes in the tree!
- You click “Refresh schema” in the context menu and now you are ok.
Described issue is not bug, but it can cause problems.
Some Wappler users, especially new ones, could not understand this behavior.
Even more confusion added because here is another schema refresh button, but it doesn’t affect the list of fields.
So, I suggest the list of tables and fields must be automatically refreshed after changes are applied.