just wanted to migrate from 2.3.0beta9 to stable release and got this error:
What can I do here ?
Caused by:
PG::UndefinedColumn: ERROR: column “email_private_messages” of relation “user_options” does not exist
LINE 1: UPDATE “user_options” SET “email_private_messages” = FALSE, …
Hey, @Falco. This is the second time this has come up in as many weeks. Maybe there should be a comment in standalone.yml and web_only.yml that says something like
## Which Git revision should this container use? tests-passed is the best-supported and recommended for most installations
rather than
## Which Git revision should this container use? (default: tests-passed)
99% of the users won’t ever see the file since ./discourse-setup hides all the complexity.
The users going to the file, and reading a commented line, researching the alternative values of the key, and opting into a different one, while managing to ignore the various warnings in Meta are difficult ones.
We could just hide the key from that commented line, making it harder to shoot yourself in the foot.
My point is that the commented line currently doesn’t give them any guidance and the knee-jerk for someone who does know what a branch is things “All I know is that my bosses want things to be stable.”
Whether to remove any hint of how to change branches or give them a stronger hint not to change it without learning a bit more is a fine question.