I have same problem, but with local target.
@George I'm kindly asking your attention to this topic, because currently Wappler is completely not usable for creating new project with database.
Here is reason with Local Database: 2024-07-01 12:50:10.912 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 15.3 (Debian 15.3-1.pgdg120+1).
Hi @Notum,
As you can see from the error the problem is not from saving the project but changing the database version to a much newer one without any migration.
So depends on what you want to do with the database and if you want to keep it, then you need to upgrade it, or initialize from scratch.
I don't think Notum will understand George's reply, it has no practical advice
@Notum destroy database data and Deploy project again:
I'm sorry, but you completely missed the essence of the problem.
I've spent 20 minutes of my time and made record bellow.
I hope this will be enough.
@George please allow to attach GIF's with more than 15Mb.
Please view my recording.
This is also my experience. Everything is working perfectly in 5.8.2, which I've had to revert to, but there is a consistent database connection error in the current version when you try to create a new project. The database gets set up in Docker, but the database manager cannot connect. There have been a few related topics, including my bug report two weeks ago.
@George I believe when @Notum says "changing version" it means changing the Wappler version. Not the postgres version. They're starting a new local project so there is no changing the database version. We're at the stage where the database is only being created.
Actually no where in my messages regarding this issue I've mentioned about "changing versions". At my very first step is 1. I've created a brand new project.
My apologies, @Notum. I got that from the title of this thread. I am having the same issue as you are, though. I raised it as a bug report two weeks ago
Actually I think your title of your post is where the confusion is. Even I understood that as an error changing database versions?
It's not my title, but @George took my topic and named it.
Ah then my apologies.
@George, would it be possible for you to try it out so you can see what we're talking about? Since 6.7's release, several database target-related topics have been posted on this in the bugs category. Something happened in the past (at least) two releases. I would provide logs but I've indefinitely reverted to 5.8.2 because the current version is unusable for me.
Yes this is exactly what I meant and you should do @Notum
The database was not available initially because you got an error indeed starting the database server because it was using a directory where previous version was stored.
So by clearing it and you create a fresh new database instance.
@TheForce i think you are talking about different problems, please open a separate topic
HI @George , @notum and I are not talking about different problems but if you need a separate topic from me, can I point you to the bug report I made two weeks ago?
The issue is that when creating a new project with a database, the current version of wappler does create a database that we can see in docker but it does not and cannot connect to the database manager. Creating a new project with a database in earlier versions of wappler does do everything properly and can also be opened and working properly in the current version. This is what @Notum is describing and also what I have been describing. Please try it so you can see what we’re talking about.
When @Notum provided this,
It was from creating a new project with a database. @Notum described that in the first post in this topic. Your response assumes it is not a brand new project, as does @Apple ’s response because @Notum even replied that you missed the essence of the problem. Why would we need to destroy database data and deploy again when all we’ve done before is create a new project with a database? Wouldn’t that mean there’s a bug in how wappler is creating the database for us? Would it be possible for you to try to create a new Docker project and a new docker database in the current version so we don’t feel like we’re going crazy? You would see what we’re talking about and that we are both talking about the same thing. My bug report was ignored and this thread is frustrating because it is easily reproduced, if only you would try it.
And as a side note, there are also posts about not being able to create connections in production targets. Could there be something with the way the current version is attempting to create database connections? Again, everything works fine in previous versions.
PLEASE TRY BY YOURSELF!!!
I really tired to show something that you can check by yourself!
Again, this is a new project!!!
