-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Comments
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. |
I see also that 3.2 uses SQLite database and 3.3 doesn't. Thanks. |
No. |
Thank you. I'll keep checking back. |
Nudge. |
@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. The tool I am talking about is: https://github.com/papermerge/pmdump |
Quick update. Utility for upgrading from 3.2 to 3.4 will be out in couple of days. |
@thndrbck what database do you use ? SQLite or PostgreSQL ? |
Sqlite
…On Sat, Mar 8, 2025, 12:45 AM Eugen Ciur ***@***.***> wrote:
@thndrbck <https://github.com/thndrbck> what database do you use ? SQLite
or PostgreSQL ?
—
Reply to this email directly, view it on GitHub
<#641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEADQQQS6ZMEXI2IMNNSZED2TJ7ZJAVCNFSM6AAAAABUYNJLCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYGA2DEOJTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: ciur]*ciur* left a comment (ciur/papermerge#641)
<#641 (comment)>
@thndrbck <https://github.com/thndrbck> what database do you use ? SQLite
or PostgreSQL ?
—
Reply to this email directly, view it on GitHub
<#641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEADQQQS6ZMEXI2IMNNSZED2TJ7ZJAVCNFSM6AAAAABUYNJLCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYGA2DEOJTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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 At this point documentation for it is only here: https://github.com/papermerge/pmdump |
I will be happy to. Tomorrow afternoon.
…On Sun, Mar 9, 2025, 3:17 AM Eugen Ciur ***@***.***> wrote:
Could you give a try to pmdump v0.2
<https://github.com/papermerge/pmdump/releases> ?
At this point documentation for it is only here:
https://github.com/papermerge/pmdump
—
Reply to this email directly, view it on GitHub
<#641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEADQQVZUUNBYYDJSDOYFGT2TPTHPAVCNFSM6AAAAABUYNJLCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYG4YDSNBUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: ciur]*ciur* left a comment (ciur/papermerge#641)
<#641 (comment)>
Could you give a try to pmdump v0.2
<https://github.com/papermerge/pmdump/releases> ?
At this point documentation for it is only here:
https://github.com/papermerge/pmdump
—
Reply to this email directly, view it on GitHub
<#641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEADQQVZUUNBYYDJSDOYFGT2TPTHPAVCNFSM6AAAAABUYNJLCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYG4YDSNBUHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: