Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change type of field "value" in table #_fields_values from text to mediumtext #42605

Closed
wants to merge 28 commits into from
Closed

Conversation

sergeytolkachyov
Copy link
Contributor

Change type of field "value" in table #_fields_values from text to mediumtext for MySQL ONLY. PostgreSQL have only text field type with unlimited length. Pull Request for Issue #36065

RickR2H and others added 27 commits December 20, 2023 13:22
… PR 42489 (#42550)

* Better English (1)

Co-authored-by: Brian Teeman <brian@teeman.net>

* Better English (2)

Co-authored-by: Brian Teeman <brian@teeman.net>

* Remove br html element from language strings

---------

Co-authored-by: Brian Teeman <brian@teeman.net>
Fixes hardening measure introduced in #23716
* load lang

* test-4-dupkey

---------
Better message on package uninstallation when an extension from that package is missing. Fixes issue #42537 .
backport [5] update from nightly to latest nightly build
#41865
* Fix `function` parameter lost during redirect

Currently if you are switching the menu filter in the menu item select modal, the function parameter will be lost on redirect.

* Move function parameter to form url

* Remove hidden input
…_SIZE rows" when checking for core updates (#42576)

* Use concat of columns for getting core extensions

* Fix PHPCS

* Remove wrong quotes
* cast to int for pgsql

* yet-another

---------
…diumtext for MySQL ONLY. PostgreSQL have only text field type with unlimited length. Related to #36065
@sergeytolkachyov
Copy link
Contributor Author

Because J5.0.2 now is RC I moved it to 5.0.3.

@sergeytolkachyov
Copy link
Contributor Author

@richard67 @HLeithner

@richard67
Copy link
Member

@sergeytolkachyov Meanwhile 5.0.x is in stable phase, so I think this PR here should be made for the 5.1-dev branch. Could you rebase your PR or redo it for 5.1-dev?

Co-authored-by: Richard Fath <richard67@users.noreply.github.com>
@sergeytolkachyov
Copy link
Contributor Author

@sergeytolkachyov Meanwhile 5.0.x is in stable phase, so I think this PR here should be made for the 5.1-dev branch. Could you rebase your PR or redo it for 5.1-dev?

Is this such a big change that it should only be in the minor version?

@richard67
Copy link
Member

Is this such a big change that it should only be in the minor version?

@sergeytolkachyov I will ask other maintainers or release managers for their opinion. Stay tuned.

@HLeithner
Copy link
Member

@sergeytolkachyov Meanwhile 5.0.x is in stable phase, so I think this PR here should be made for the 5.1-dev branch. Could you rebase your PR or redo it for 5.1-dev?

Is this such a big change that it should only be in the minor version?

it's a feature and not a bugfix that's the reason why it should go into 5.1.

@sergeytolkachyov
Copy link
Contributor Author

sergeytolkachyov commented Jan 4, 2024

If you follow the semver, minor releases should include changes that do not lead to loss of backward compatibility and lead to the appearance of new functionality. While minor changes, bug fixes should be included in the patch version. As a result of applying the changes from this PR, nothing new will appear for either developers or users. The bug described in the issue will only be fixed.
Why is this a feature? Maybe for languages using the Latin alphabet, this is a feature - an increase in the amount of data for the field. But for languages where letters are stored in unicode, this is rather a bug fix, since it was impossible to store a large amount of data in the field values.

@sergeytolkachyov
Copy link
Contributor Author

There is really no big difference when it will be enabled: in 5.0.3 or in 5.1. I just want to understand the logic.

@HLeithner
Copy link
Member

everything which is not a bug is a feature, if you follow this you simple reduce the pain to upgrade. security stuff is another topic and a change like this doesn't need to hurry since you can fix it for your sites your self.

@sergeytolkachyov sergeytolkachyov changed the base branch from 5.0-dev to 5.1-dev January 4, 2024 10:03
@@ -0,0 +1 @@
ALTER TABLE `#__fields_values` MODIFY `value` MEDIUMTEXT;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rename the script from "5.0.3-2024-01-04.sql" to "5.1.0-2024-01-04.sql".

@sergeytolkachyov
Copy link
Contributor Author

@sergeytolkachyov Meanwhile 5.0.x is in stable phase, so I think this PR here should be made for the 5.1-dev branch. Could you rebase your PR or redo it for 5.1-dev?

Is this such a big change that it should only be in the minor version?

it's a feature and not a bugfix that's the reason why it should go into 5.1.

It seems to have done a rebase...

@richard67
Copy link
Member

It seems to have done a rebase...

@sergeytolkachyov Yes. Now the PR shows more changes than only yours, and there are conflicts, but I think that should be solved with the next upmerge from 5.0-dev to 5.1-dev by the release managers and then updating your branch to the 5.1-dev.

In addition it needs to rename the update SQL script, see my review comment.

So maybe it's easier if you just close this PR and make a new one for the 5.1-dev branch.

@sergeytolkachyov
Copy link
Contributor Author

sergeytolkachyov commented Jan 4, 2024

So maybe it's easier if you just close this PR and make a new one for the 5.1-dev branch.

I made a #42606

@richard67
Copy link
Member

Thanks.

Razzo1987 pushed a commit that referenced this pull request Jan 26, 2024
…diumtext for MySQL ONLY. PostgreSQL have only text field type with unlimited length. Pull Request for Issue #36065 and remake a PR #42605 for Joomla 5.1.0 (#42606)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet