Path length in database needs to be higher #167
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.
Some of the users on my server had used paths longer than 191 characters, and this breaks the cache rebuild process.
Server output:
Server# sudo -u www-data php occ carnet:cache rebuild
list of user files
/username/files/Documents/QuickNote/companyname/Á###á####/#######ó á###á######/500- 700 #á#á### #####é# 6 ##á###é#. #ö###á# #6 #7 ##########á# #ö#######á#. #ő#### #######é## 800 1000 ####### ####á## ##á##ő##é# ####á# .sqd (the problematic file, private information blanked out)
In ExceptionConverter.php line 114:
An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'path' at row 1
In Exception.php line 26:
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'path' at row 1
In Statement.php line 82:
[22001]: String data, right truncated: 1406 Data too long for column 'path' at row 1