#5707 closed defect (duplicate)
MySQL - primary key in table node_change
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control | Version: | |
| Severity: | minor | Keywords: | mysql | 
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The column path in the table node_change is text. This means mysql automatically will treat uppercase letters as lowercase letters. If you have now a repo where two different files have the same path and name, but one is in uppercase (my/path/Test) the other in lowercase (my/path/test), you are running into a primary key violation (path is part of the primary key).
I found a workaround for this. I changed the path from text to varbinary: http://dev.mysql.com/doc/refman/5.1/en/binary-varbinary.html
Worked for me. Need to see how much this will influence the performance.
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
| Component: | general → version control | 
|---|---|
| Keywords: | mysql added | 
| Owner: | changed from to | 
comment:2 by , 18 years ago
| Resolution: | → duplicate | 
|---|---|
| Status: | new → closed | 
comment:3 by , 18 years ago
Just as a follow up on this one. I am still working with this workaround and the system is live and running under full steam without any issues.



  
Expect encoding issues with your workaround.
See also the warning in DatabaseBackend#MySQL.
Duplicate of #4378 / #3676.