If I interpret this issue correctly, the parameter has completely been removed and instead the default parameter value is set to “nc_” with a fallback to “oc_”?!
Although the following post mentions that the prefix should have been changed to “nc_”, I seems that the Nextcloud code itself always uses “oc_” as a prefix?!
@nickvergessen a warning that the option was removed would have been nicer than exit with an error. occ maintenance:install would still be able to initialize nextcloud.
that wouldn’t break automated installation scripts like my playbook.
@Reiner_Nippes Did you already run some tests with the new version? Can you tell me which prefix will now be used by default, “nc_” or “nc_”? I think I have to test my own scripts too to make sure they’re still working as expected
Well I think it’s better to get an error instead of secretly ignoring it, especially because of scripts like this where people would wonder why the parameter doesnt work in the end.
It’s a simple fix on your side this way, otherwise you at some point would have debugged for ages just to find out the parameter is not working anymore.
The prefix is oc_ and should not be changed. There are a lot of issues with oracle and length of table names, index names etc. and it also makes sure that database queries posted in the forum, docs and other places work for everyone.
The parameter was removed from the install screen already for a long time, only the command was missed back then.