Wappler Version : 4.0.3
Operating System : Windows 10
Server Model: nodejs
Database Type: MariaDB
Hosting Type: local
Expected behavior
What do you think should happen?
When editing database connections to point to say eg: a different database that it connects successfully to the new db
Actual behavior
What actually happens?
The updated db connection updates for database manager correctly, but not for api’s
How to reproduce
- I duplicated a Wappler project that uses a mariaDB database, and didn’t want to use the same db.
- So I created a new db, and pointed the duplicated Wappler project’s db connection to new db.
- Then used Wappler DB manager changes / migration scripts to create existing db structure, which worked perfectly
- Next I created a new table using Wappler database manager, which worked fine, checked it in navicat
- Then I created an api with a simple select query, which when run reported my new table does not exist in db.
Create new database connection, which produces
and
Next I edit the Wappler database connection and changed database name from “test_db_playpen” to “test_db_playpen_tmp”, which produced the following
and
Community Page
Last updated:
Last updated: