Change DB field type of persparam fields

English forums
1

Oxid 4.9.9

Does it have any negative side effects to change the type of this field from text to mediumtext? The background is that we use this field to store some additional data but the customer did a lot more than was initially communicated. About 5% of the entries in the DB have exceeded the 65535 character length limit of the field, resulting in data loss.

As an emergency solution we are currently storing the data elsewhere in parallel, so we can fix the broken entries, but I want to make sure to not break something that may not be immediately obvious by changing the DB field type. Under normal circumstances, this shouldn’t be an issue, but I saw oxid using table meta information somewhere so I’m worried weird things will happen.

TL;DR:
Can I simply change oxuserbasketitems.persparam and oxorderarticles.persparam to the mediumtext field type?

2

Hey @Anpan,

I reckon the meta information are only used for documentation purposes.
On the other hand, I can’t really tell you what happens if you switch to mediumtext. Best would probably be to check it out in your dev environment and test it extensively before going public with it. Anyway, I’d be interested in the results.

Cheers