- 🇺🇸United States rraney
Hello - what's the recommended solution or workaround for this issue currently? Which version of the module doesn't use SQL Triggers? Is it still 1.x(3.x in D10) or has there been another update?
Triggers are not supported everywhere but with MySQL 5.6 reached EOL in February 2021 we can require MySQL 5.7 and use virtual index.
InnoDB supports secondary indexes on virtual generated columns. Other index types are not supported. A secondary index defined on a virtual column is sometimes referred to as a “virtual index”.
See https://dev.mysql.com/doc/refman/5.7/en/create-table-secondary-indexes.html
As for PostgreSQL, just join on the CAST expression without any tricks because PostgreSQL can index on such a thing. In late 2023 when MySQL 5.7 is EOL and hopefully MariaDB catches up too, we can drop the generated column and standardize on this -- MySQL 8.0 can index on expressions right now, MariaDB can't.
Finilize the apporoch.
Create a patch
Add upgrade path
Create a new branch. maybe
Commit
Release
Rejoice
None
Triggers will be removed.
Virtual Index will be used.
Extra string column for target ID becomes maintained by the database without triggers.
Active
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Hello - what's the recommended solution or workaround for this issue currently? Which version of the module doesn't use SQL Triggers? Is it still 1.x(3.x in D10) or has there been another update?
