Database Multiple Bugs Report from bradyneal #2021-6-12_16-37-5

Wappler General Bugs
,
1

Prelude

Most of the bugs I’ve been experiencing with Wappler seem to be related to the Database Manager. In this bug report, I show 3 bugs. I’ve attached a video and give the timestamps of each of the bugs.

OS info

  • Operating System : Mac OSX 19.6.0
  • Wappler Version : 3.9.9

Problem description 1 (3:36 in video)

Database tables (and schemas if the database type has them) don’t show up. It shows “No schema info available…” The Refresh button does not fix this. I’ve found that restarting Wappler generally fixes this for me, though (see video).

Steps to reproduce 1

  1. Create blank Wappler project.
  2. Set database in target (to PostgreSQL or another; doesn’t seem to matter).
  3. Go to Database Manager and access the tables.

Problem description 2 (4:20 in video; blaze)

"Fetch Data" not there after clicking “View/Edit Data” on a database table. Note: I tried restarting Wappler several times because I believe this usually fixes the bug for me. I also tried refreshing the database folders and re-deploying to see if those fixed it.

Steps to reproduce 2

  1. Perform the above steps (blank project and add database) and restart Wappler if necessary to get past the above bug.
  2. Click “View/Edit Data” on a table in the Database Manager
  3. Observe that “Fetch Data” isn’t there.

Problem description 3 (7:43 in video)

Database tables won’t rename. It seems like Wappler is looking at the newly renamed table as the old table when it looks at the migration file. Note: this problem is really several sub-problems in one:
a) Wappler gave a “Database Changes Applied Successfully” toast at 8:01, but it seems change wasn’t actually applied (see 8:29).
b) Wappler errors when renaming the table (see, e.g., 8:17, 9:03, etc.).
c) Wappler actually did rename the first table (not the second)? See that the “cars” table is actually “cars2” after I refresh at 8:50. But the “cars” rename still shows up in the migration file, so it wasn’t actually applied (as mentioned in bug 3a)?

Steps to reproduce 3

  1. Perform the above steps (blank project and add database) and restart Wappler if necessary to get past the first bug.
  2. Rename a database table.
  3. Apply the database changes.
  4. Maybe go back to step 2 and repeat once more (like in the video).

report_2021-6-12_16-37-5.zip (92.0 KB)

db_rename_table_bug

3

Just tested with my colleague, and he also observes these bugs in Wappler 3.9.9 on a much newer OS: Big Sur v.11.1

4

What kind of database are you connecting to?

5

Also do note that when starting up docker databases - it takes a while to get the database server running.

So try to refresh in the database manager when all services are running first.

6

Postgres (1:42 in video).

7

Database comes online at 3:36 in video, and that’s when I start doing things (the Docker server and database startup time is why the first timestamp is after 3.5 minutes).

8

Yes I saw that you were doing all kind of database changes at 2:47 while the services were still starting up.

After restart and normal startup all seems fine and tables schema us retrieved.

Please file separate issues for the different problems if those are still valid. This will help us track those better.