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

Upgrade issue 3.2 to 3.3 #641

Open
thndrbck opened this issue Jan 7, 2025 Discussed in #640 · 11 comments
Open

Upgrade issue 3.2 to 3.3 #641

thndrbck opened this issue Jan 7, 2025 Discussed in #640 · 11 comments
Assignees

Comments

@thndrbck
Copy link

thndrbck commented Jan 7, 2025

Discussed in #640

Originally posted by thndrbck January 7, 2025
I did an in place upgrade of PM version 3.2 to 3.3.
None of the documents I had uploaded, nor the folders I had made in 3.2 were visible in 3.3.
I downgraded back to 3.2 and everything was back to normal.

I'm using Portainer to manage my containers. I followed the procedure for upgrade that I've used in the past to go from 3.0 to 3.1 to 3.2. I have that procedure documented and it's worked in the past.

Any advice on upgrading will be appreciated. Need the field feature.

@ciur
Copy link
Owner

ciur commented Jan 8, 2025

The problem is that i renamed all underlying database tables in 3.3.

Basically table "core_user" is now "users", "core_basetreenodes", is now "nodes". "core_folders" is now "folders" etc.

So, yes, it won't work just to change the docker image.

@thndrbck
Copy link
Author

thndrbck commented Jan 8, 2025

I see also that 3.2 uses SQLite database and 3.3 doesn't.
So what's the best way to bring my instance up to 3.3?
Will a backup of 3.2 restore to 3.3? If so, Is there anything to be done with the persistent folders?

Thanks.

@ciur
Copy link
Owner

ciur commented Jan 8, 2025

No.
But I will fix the import into 3.3 part; it is not that complicated.
Currently I am busy with updating landing page and adding an online demo instance. Once I am done with that, I will deal with import from 3.2 into 3.3 issue.

@thndrbck
Copy link
Author

thndrbck commented Jan 8, 2025

Thank you. I'll keep checking back.

@thndrbck
Copy link
Author

Nudge.

@ciur
Copy link
Owner

ciur commented Feb 22, 2025

@thndrbck this is work in progress. In couple of weeks I will release a separate tool (pmdump, a binary) with which you will be able to export all data from 3.3 into a tar.gz and then import that tar.gz into 3.4.
Actually tool is being designed to be able to export data also from and 2.0, 2.1, 3.3.

The tool I am talking about is: https://github.com/papermerge/pmdump
It is in very early stage of development i.e. work in progress. Still experimenting.

@ciur
Copy link
Owner

ciur commented Mar 7, 2025

Quick update.

Utility for upgrading from 3.2 to 3.4 will be out in couple of days.

@ciur
Copy link
Owner

ciur commented Mar 8, 2025

@thndrbck what database do you use ? SQLite or PostgreSQL ?

@thndrbck
Copy link
Author

thndrbck commented Mar 8, 2025 via email

@ciur
Copy link
Owner

ciur commented Mar 9, 2025

Could you give a try to pmdump v0.2 ?

With it you can export data from Papermerge DMS 3.2 (running on sqlite database) and import it into
Papermerge DMS 3.4 - either sqlite or postgres database.

At this point documentation for it is only here: https://github.com/papermerge/pmdump

@thndrbck
Copy link
Author

thndrbck commented Mar 9, 2025 via email

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

No branches or pull requests

2 participants