Defect #38184
Production ready database back-ends - wiki update
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Documentation | |||
| Target version: | - | |||
| Resolution: | Affected version: |
Description
Recently my company was performing a big Redmine deploy (4.2.X with SQL Server). After sometime users started to complain about issue hierarchy getting corrupted.
We made a research and it turns out there is a workaround in issue nested set locking for SQL Server which is behaving wrong sometimes (when multiple users are editing same issue trees). This is a BIG thing and is really surprising that there isn't a word about in the Installation guide. I think there should be a noticeable information that the only production ready database back-ends are MySQL 5.5 and PostgreSQL 9.2 +.