Open Eddcapone opened 1 month ago
Hi @Eddcapone. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hello @Eddcapone,
Thank you for the report and collaboration!
As there is no way to set collation using declarative schema, this can be considered as feature request.
Summary
There is currently no way to set the collation of a column by using declarative schema.
Examples
Try to set the collation of the column detail from the review_detail table to utf8mb4_unicode_ci via declarative schema.
It will not work.
You are then forced to use a Setup/InstallSchema.php script to change the column like so:
Then execute
php bin/magento setup:upgrade
to make it install that schema.Problem: The next time you call
php bin/magento setup:upgrade
, it will override it again because it will find the instruction in the declarative schema @ vendor/magento/module-review/etc/db_schema.xml, to override it again.Proposed solution
The solution would be, to be able to set the collation in a declarative schema file, so we could override it from a custom extension.
Release note
No response
Triage and priority