Wappler Version : 3.7.6
What do you think should happen?
I created a table and the fields are suposed to be shown
What actually happens?
There is a message "No columns info avaiable" and on properties:
An error has ocurred connecting to the database!
Make sure you have entered the right connection info at target options
Create an app with node.js and postgres database + docker
Create a table with PK as BIG INCREMENT
Below, some screens showing the docker container is started correctly and the project settings:
Below, the successfully connection test on database manager:
UPDATE: I downgraded Wappler to 3.7.4 and the error remains the same and PLUS: news changes are not working, but rollback changes are!!
JonL
February 16, 2021, 5:02pm
2
On 3.7.2 everything is fine. So I guess the bug appeared in 3.7.3 or 3.7.4
Hey Jon, Thanks! Where can I find de 3.7.2?
JonL
February 16, 2021, 5:05pm
4
Same place you found 3.7.4 but changing the 4 for a 2 I’m guessing
Just tried, page not found…
https://wappler.io/downloads/Wappler-Mac-3.7.2.dmg
3.7.3 is avaiable, I’ll give a try
1 Like
with 3.7.3, same error! @George would be great to have the version 3.7.2 available or a temporary workaround, I’m stuck with this problem!
George
February 16, 2021, 5:59pm
8
It should really be all fine in 3.7.4
What error do you get? Nothing is changed there.
Hey George! Thanks! No errors, even on Postgres Log...only wappler message, as images on my post:
There is a message “No columns info avaiable” and on properties:
An error has ocurred connecting to the database!
Make sure you have entered the right connection info at target options
George
February 16, 2021, 6:02pm
10
On all your existing tables or just the one you created with bigincrements? Bigincrements wasn’t available before so don’t use it
George
February 16, 2021, 6:21pm
12
Please restart Wappler with logging, reproduce the problem and attach the debug log. See:
Updated for Wappler Version 5.0 and higher
We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log.
Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging.
You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging”
Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report … o…
George
February 16, 2021, 6:24pm
13
And what about your existing databases? Do you get the same error everywhere? Or just on new database with new table?
JonL
February 16, 2021, 6:35pm
14
Some additional info from my side:
I don’t have problems on 3.7.2 on already existing databases. I haven’t tried creating a new one.
George! Here is the log!report_2021-1-16_15-40-31.zip (351.0 KB)
Others databases (mySQL) are working…This is my first postgres database.
George
February 16, 2021, 6:47pm
16
Sorry there is not much in the log - did you went to the database manager and refreshed the schema? when logging was on?
Did this right now, here is the log:
report_2021-1-16_15-48-20.zip (319.5 KB)
But seems the refresh button is not working. I’m not sure.
George
February 16, 2021, 6:54pm
18
Ha! Good catch!
It has something to do with your mixed case naming of the database table and columns!
I will investigate further, but for now if you just keep your table names and fields to lower case it should be all fine.
George
February 16, 2021, 7:12pm
20
Anyway found the issue and it will be fixed in the next update
