[5.3] Change type of field "fieldparams" in table #_fields from text to mediumtext

[alikon]

Pull Request for Issue #43929 .

Summary of Changes

alter #__fields.fieldparams to MEDIUMTEXT

Testing Instructions

run the sql

ALTER TABLE `#__fields` MODIFY `fieldparams` MEDIUMTEXT NOT NULL;

or
https://artifacts.joomla.org/drone/joomla/joomla-cms/5.3-dev/44238/downloads/79556/

Actual result BEFORE applying this Pull Request

the field is TEXT

Expected result AFTER applying this Pull Request

the field is MEDIUMTEXT

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed

[fgsw]

I have tested this item ✅ successfully on 03a0fab

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44238.}

[richard67]

I've restored the previous human test result as the later changes which have invalidated the test counter were only some kind of code style without functional impact.

[richard67]

I have tested this item ✅ successfully on 8270392

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44238.}

[richard67]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44238.}

[laoneo]

Do we not need the changes on postgres too?

[richard67]

Do we not need the changes on postgres too?

@laoneo No. PostgreSQL doesn’t know mediumtext or so, it uses TEXT which can be if unlimited length. See also PR #42606 .

[laoneo]

Thanks!

[Fedik]

Oh, hold on, why? It is mistake.
We should not encourage developers to store huge amount of data in parameters.
Extensions, modules, templates, menu, have the text type for parameters, why fields hould be diferent?

[laoneo]

This here is more about end users and not extension developers as the fieldparams column contains the options from the UI.