This website requires JavaScript.
Explore
Help
Sign In
AS1024
/
itflow
Watch
1
Star
0
Fork
0
You've already forked itflow
mirror of
https://github.com/itflow-org/itflow
synced
2026-11-17 01:47:25 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
fd360b35b9bb2f4dba0fc6ad5c9dfd25b871e5de
itflow
/
admin
/
database_updates
/
3.6.5.php
johnnyq
81ea84b71e
Bring every table to one collation on upgraded installs: database 3.6.5 changes any ITFlow table whose default collation or any text column is not utf8mb4_general_ci, in practice the 22 tables that 2.1.6 to 2.4.1 created without a COLLATE and that took the server default, utf8mb4_0900_ai_ci on MySQL 8 and utf8mb4_uca1400_ai_ci on MariaDB 11.5 and later, which is what made the reprice UNION fail and the dashboard come up blank; it reads information_schema so a table already right is not touched and a second run changes nothing, and db.sql is unchanged; each table is one ALTER of MODIFYs built from its own SHOW CREATE TABLE lines with only the collation replaced, in place of CONVERT TO CHARACTER SET as 2.0.6 used, so calendars.calendar_feed_key and user_calendar_feeds.feed_key stay utf8mb4_bin and no column type changes; columns with a binary collation and tables that are not ITFlow's are left alone; NO_ZERO_DATE and NO_ZERO_IN_DATE are lifted for the connection while it runs because records.record_updated_at defaults to a zero date and MySQL 8 otherwise refuses any ALTER of that table; a table that cannot be changed is left as it was with a warning in App Logs and the PHP error log and the update carries on; run on MySQL 8.0 and MariaDB 10.11 against the whole schema with a row in every table; CONTRIBUTING.md now says a CREATE TABLE in a migration ends with the COLLATE; update the 26.11.7 changelog section
2026-11-11 20:21:03 -05:00
12 KiB
Raw
Blame
History
View Raw
Reference in New Issue
View Git Blame
Copy Permalink