Remove unecessary constraint on database name #19654
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Installation of nextcloud prevents database name to have dots inside.
This is not a limitation of database (Postgres and Mysql supports this), but an added constraint added out of the blue.
Nextcloud should not add limitation of their own. I'm installing broad list of services, and none of them have ever decided to enforce their own naming constraints by preventing their installation if we don't follow them. I'm using in my case the domain name of the service as database name (as another reporter of this bug did).
This topic was mentioned a few time in issues in owncloud, but these are locked and closed. However, it hits nexcloud the same.
owncloud/core#19390
owncloud/core#20381
Removing these 3 lines will make everything work for me on postgres...
How can I help more ? Many thanks.