Probably unnecessary MariaDB global configuration change requirement
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
According to
Nextcloud requires non default MariaDB settings
transaction_isolation = READ-COMMITTED
binlog_format = ROW
Accoring to
https://help.nextcloud.com/t/transaction-isolation-level-of-nextcloud-database/88858/4
Nextcloud already sets transaction_isolation for its sessions.
Accroding to
https://mariadb.com/kb/en/binary-log-formats/#configuring-the-binary-log-format
binary log format may be configured per session too but I didn't find such solution in Nextcloud source.
Describe the solution you'd like
Please verify and consider removing MariaDB global configuration change requirement for transaction_isolation and binlog_format if not absolutely required (Nextcloud should configure own sessions only); don't not force admin to globally change default db server settings if not required as it may interfere with other applications using other databases on same server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reviewing the linked MariaDB configuration documentation and searching the Nextcloud source for transaction_isolation and binlog_format handling; done means verifying whether both settings are required globally and updating the relevant configuration documentation or implementation accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, php
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100