View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006164||OXID eShop (all versions)||4.01. Database handling||public||2015-06-11 14:20||2018-10-19 12:25|
|Product Version||4.9.3 / 5.2.3|
|Target Version||Fixed in Version||6.0.2|
|Summary||0006164: max size of BLOB for oxconfig.oxvarvalue can be exceeded|
|Description||Having a highly modifyed EE with a huge amount of extensions the maximum size 64KB for the datatype BLOB auf oxconfig.oxvarvalue can be exceeded. |
This leads into a complete breakdown of the OXID module system and the shop goes offline because there is no check if the max size of oxvarvalue will be exceeded when adding new entries.
Reaching the maximum of 64KB the data of oxvarvalue is truncated at the maximum byte which leads into an incomplete serealized array and the shop will stop working.
Changing to MEDIUMBLOB and reinstalling all modules solves the problem.
At least for Enterprise Edition this should be default and all editions should get a check to avoid running into this problem.
|Additional Information||0005948 was closed without changes and the note that this case is unusual.|
Assuming that most EE will be highly modified this should be deemed as a usual use case.
|Tags||No tags attached.|
|MySQL Version||Not defined|
|related to||0005549||resolved||saulius.stasiukaitis||module-name and value-name of module-settings limited by oxmodule-/oxvarname-field-length|
|related to||0006090||confirmed||Field oxtplblocks.oxmodule is too short|
|has duplicate||0005948||closed||Linas Kukulskis||DB : column type BLOB for oxconfig.oxvarvalue is not sufficient in some productive scenarios|
While possible, there is no known impact of this issue until now.
Though, it would make sense to extend said BLOB field to MEDIUMBLOB in future releases to play it safe.
IMHO this is a (valid) feature request.
We have got the same problem...
IMHO it's a bug. There are no communicated module limitations. In our case (ca. 80 modules) this "feature request" crashes the shop.
This is a bug, clearly, because the shop just does not validate length of the content its going to put into the database. Same "just a feature"-feeling like when hitting https://bugs.oxid-esales.com/view.php?id=5549
nothing documented, but working (maybe not as wished) -> feature or bug
nothing documented, and breaking the shop -> bug
||having the same problem using MEDIUMBLOB helped|
||same problem again, pull request for current shop version: https://github.com/OXID-eSales/oxideshop_ce/pull/633|
||Maybe instead of pushing the limit this should result in some technical redesign. In the meantime there should be limitation-checks which get reported into the logfiles, or even not being able to activate such modules.|
||Thanks, the Pull request 633 was merged to 6.x and master.|