Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Project page points about wrong state about mysql support of json
Proposed resolution
Update code and project about mysql 5.7.8 json data type
Remaining tasks
Add mysql version check in install
update project page
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#10 | 2647512-1.patch | 4.8 KB | kevinquillen |
#9 | 2647512.patch | 5.47 KB | kevinquillen |
Comments
Comment #2
kevinquillen CreditAttribution: kevinquillen commentedComment #3
kevinquillen CreditAttribution: kevinquillen commentedComment #4
andypostno patch to review
Comment #5
mikl CreditAttribution: mikl as a volunteer commentedI've already implemented this on the 7.x-1.x branch, the code could probably be lifted from there :)
Comment #6
kevinquillen CreditAttribution: kevinquillen commentedNow that MySQL 5.7.7+ is available to most people from official distros, we can make some progress here.
I am going to rebuild my Drupal VM and see what we can move on here.
Comment #7
andyposta kind of killswitch would be great to have a fallback to text-blob if mysql has no support
Also version should not be hard requirement to install the module
Suppose having message at reports/status is good
Comment #8
kevinquillen CreditAttribution: kevinquillen commentedI agree with that, is there any better way to signal to a user that the module isn't going to do a lot for them beyond the report page?
Comment #9
kevinquillen CreditAttribution: kevinquillen commentedHere is an initial patch that addresses the version checking in the .install
Comment #10
kevinquillen CreditAttribution: kevinquillen commentedHere is a better patch that simplifies things, since we just want to inform the user.
Comment #11
kevinquillen CreditAttribution: kevinquillen commentedComment #12
andypostYes, that make more sense!
Comment #14
kevinquillen CreditAttribution: kevinquillen commentedComment #15
kevinquillen CreditAttribution: kevinquillen at Velir commentedComment #16
kevinquillen CreditAttribution: kevinquillen at Velir commented