Skip to main content


friendica 2021.06 to 2022.02 db structure?


@Friendica Support due to me not being a git person, i updated from 2021.06 straight to 2022.02, do you know if i missed some db restructuring that will haunt me down the line due to that?

Friendica Support reshared this.

in reply to felix b. ohmann

Apparently it came through the forum so you're good. The difference between @ and ! is that in the latter case, the post doesn't appear in your own statuses, only in the forum's.
in reply to felix b. ohmann

You're good, we do a diff between the current structure and the target structure to determine which upgrade to make, we don't have static upgrade scripts, although even in this case it would run the scripts from both 2021.09 and 2022.02 in order.
in reply to felix b. ohmann

it would not let me !-tag the helpers when i originally wrote the post, will keep an eye open for why that happened. thanks for the clarification.
in reply to felix b. ohmann

also, i guess at least some people using git to install friendica might fall over the update instructions. maybe they could be appended by the neccessary steps... since i was still on 2021.06, i should have done

git fetch --all --tags
git checkout tags/2021.09 -b 2021.09-branch
git branch --set-upstream-to=origin/stable 2021.09-branch

and then pull 2021.09 but the 2022.02 post just references "if you are below 2021.09, update to that version first" with a link to the original 2021.09 press release, which just asks the users to pull "stable", which will update to whatever is the latest version (in my case 2022.02). i know i should learn git properly, but i use is so sparsely that stuff like this gets me every time. :)
in reply to felix b. ohmann

Ah, I see what you mean about installing gradually. I'm not sure why we need admins to upgrade to 2021.09 first.
in reply to felix b. ohmann

maybe writing the blog release posts in a way to explicitly switch to the tag they are about could help git beginners not run into this if they come from older versions. good that it worked. :)