Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collaborative map doesn't exist after upgrade #291

Open
seljuck opened this issue Jul 12, 2024 · 8 comments
Open

collaborative map doesn't exist after upgrade #291

seljuck opened this issue Jul 12, 2024 · 8 comments

Comments

@seljuck
Copy link

seljuck commented Jul 12, 2024

Hello,

I did a docker compose pull on my Facilmap container last week, and now I get this error message trying to pull up a collaborative map

Error opening map
This map does not exist.

image

Is there any way to get it back?

Thanks,
Daniel

@cdauth
Copy link
Contributor

cdauth commented Jul 13, 2024

That's strange! What database are you using?

In the latest image, the Pads table was renamed to Maps. Maybe something went wrong during the rename? Could you inspect your database and see whether the Pads database still exists and contains your maps?

@seljuck
Copy link
Author

seljuck commented Jul 13, 2024

I'm just using the one that's called form the standard docker-compose.yml file, postgis

The Pads table does still exist, and there is no Maps table.

@seljuck
Copy link
Author

seljuck commented Jul 17, 2024

Can I manually change the table name myself? Or is there a way automatically have the table name change?

@cdauth
Copy link
Contributor

cdauth commented Jul 18, 2024

If you don't have a Maps table yet, you are still on v4. I'm not sure what could have gone wrong here. Could you just inspect the Pads table and see if you find your map there, and whether it still has the same id, writeId or adminId that you were using before?

@seljuck
Copy link
Author

seljuck commented Jul 19, 2024

I'm in the psql cli and I use the command
/d Pads
It gives me the error "Did not find any relation Pads"
In fact it gives me that error for any table in the Public Schema. But it will display tables that are in the tiger schema.

@tio-trom
Copy link

Same for me. I am using the Yunohost package https://github.com/YunoHost-Apps/facilmap_ynh - I have lost the saved maps unfortunately, all after the update.

@cdauth
Copy link
Contributor

cdauth commented Sep 5, 2024

Have you found out anything new in the meantime? Has the problem maybe solved itself after pulling and updating again?

I find it pretty hard to investigate this remotely without having access to the database. Would it be an option for someone who has this problem to share their database? Maybe could you investigate the database a little bit? What tables are there, do they still contain the data of your lost maps?

@tio-trom
Copy link

tio-trom commented Sep 8, 2024

The 4.1.2 fixed it for me! Yes! I can find the saved maps again! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants