-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[12.0] [WIP] database_cleanup: migration to 12.0 #1408
Conversation
Great! No, nobody is working on this yet, so I assign you in #1368 |
cc98141
to
a432c49
Compare
@pedrobaeza should be good now ! |
e6562fe
to
ebeb03b
Compare
Teste with a module migration use case from V11, which was also done in v12. Almost all seems like working OK, except for a weird behavior which I couldn't reproduce again when Purging all columns; after doing that it started complaining that my user (admin 1) didn't have enough priviliges when clicking on all menus. After a refresh a 403 Forbidden was raised. After restoring a snapshot and doing the process again, this did not happened; and everything seems working as expected. |
Found the culprit; it's the |
I've tested it out on the v12, works well. However I found |
#1507 should be included here. |
@pedrobaeza Don't you think we can merge and add a comment in roadmap to cherry pick v11 changes . |
@bealdav this shouldn't be merged until the passwords issue is solved (at least): #1408 (comment) P.D.: I'm using it already, with this PR, knowing that I have to remove the password table from being purged. But someone can have a really bad moment not knowing this. |
Well, that comment means to not do it ever, and that changes are very important, even possibly solving @gustavovalverde's issue. If you want to retake the migration and add that PR, it's very straight-forward. |
ebeb03b
to
f237496
Compare
Hey @mart-e, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
@mart-e has just pushed an updated branch. Please check your issue, @gustavovalverde |
Hi, Sorry for the lack of replies. I will try to fix the remaining issue. |
Thanks! |
cf discussion on OCA#1408
1b9383e
to
ab29152
Compare
cf discussion on OCA#1408
I have also picked the commits from #1507, I hope it was the only ones. |
ab29152
to
6a3a0c8
Compare
cf discussion on OCA#1408
@bealdav and @paulius-sladkevicius could you guys check and approve if everything is working as expected? |
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
cf discussion on OCA#1408
Syncing from upstream OCA/server-tools (16.0)
As part of the hacktoberfest, I am starting to migrate the module database_cleanup to 12.0 (hopefully nobody is working on it yet).