User tests: Successful: Unsuccessful:
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 and remake a PR #42605 for Joomla 5.1.0
Joomla_5.1.0-alpha3-dev+pr.42606-Development-Full_Package.zip
#__field_values
table. Then go to structure section and check that type of value
field is mediumtext
.value
field type in PHP My Admin in #__field_values
table. It is a text
type now.Joomla_5.1.0-alpha3-dev+pr.42606-Development-Update_Package
and update#__field_values
table - type of field value
. It could be a mediumtext
Status | New | ⇒ | Pending |
Category | ⇒ | SQL Administration com_admin Installation |
@sergeytolkachyov You reacted with a thumbs up to my previous comment, but you haven't added any testing instructions to the description of this PR yet. Could you do that? Thanks in advance.
@sergeytolkachyov You reacted with a thumbs up to my previous comment, but you haven't added any testing instructions to the description of this PR yet. Could you do that? Thanks in advance.
Yes, I'll do that
Just an off topic comment, if you working heavily with custom fields: you can improve the performance enormous when you change the item_id
column to integer instead of varchar.
But for this change we need a small kind of migration, but I think worth to investigate (if you're up for another PR)
@sergeytolkachyov You reacted with a thumbs up to my previous comment, but you haven't added any testing instructions to the description of this PR yet. Could you do that? Thanks in advance.
Done
Done
Thanks.
Just an off topic comment, if you working heavily with custom fields: you can improve the performance enormous when you change the
item_id
column to integer instead of varchar.But for this change we need a small kind of migration, but I think worth to investigate (if you're up for another PR)
@bembelimen It did that in my application with about 40k fields_values and it makes such an incredible huge difference. I would really appreciate and support a PR for that.
@richard67 @bembelimen not merged?
@sergeytolkachyov You should know that
quite every pr needs 2 human test
I have tested this item ✅ successfully on a7badaa
code review
quite every pr needs 2 human test
Yes, if it’s not just a typo in a comment, that’s what I mean with „non trivial“.
Strangely, for some reason I remembered that 2 necessary tests had already been done.
Strangely, for some reason I remembered that 2 necessary tests had already been done.
@sergeytolkachyov Where? Here in the PR I can not see any human test results except of the one from a few minutes ago.
Strangely, for some reason I remembered that 2 necessary tests had already been done.
@sergeytolkachyov Where? Here in the PR I can not see any human test results except of the one from a few minutes ago.
I wrote to 3 humans for testing now. Thank you
I have tested this item ✅ successfully on a7badaa
Successfully tested
Status | Pending | ⇒ | Ready to Commit |
Labels |
Added:
Feature
PR-5.1-dev
|
RTC
Labels |
Added:
RTC
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-01-26 12:00:43 |
Closed_By | ⇒ | Razzo1987 |
Thanks!
@sergeytolkachyov By review your PR looks good to me. But it would be good if you could provide some testing instructions. When you create a pull request, there are already headings for testing instructions and so on in the description. This is intended to be completed by the author, not to be removed completely. Possible testing instructions could be to make a new installation and check the type of the column after that, and to make an update with the package ur custom URL created by drone and check the type of the column after that. Or in this simple case maybe only "Code review". But there should be some testing instructions.