The best thing we can do is catch it and skip rather than fail hard

In T8715#176393, @RhinosF1 wrote:

The best thing we can do is catch it and skip rather than fail hard

Hm, how could we do that?

Fork the script and catch the error the same way you would any php exception

For future reference,

ALTER TABLE searchindex ADD FULLTEXT INDEX si_title (si_title), ADD FULLTEXT INDEX si_text (si_text);

Would fix the problem on wikis with a searchindex without the need to run rebuildtextindex when they experience an error regarding not having a FULLTEXT index.

Thanks @John, that's noted and in the future I'll be using that.

In the meantime my question is, is there really absolutely nothing that we can do for wikis that have unfortunately already been rebuilt?

It would seem then that we could do ALTER TABLE searchindex MODIFY COLUMN si_title MEDIUMTEXT; to resolve the issue on affected wikis?

Diverging from core schema is not a fun idea for me when I get to do releases

Thank you!

Thank you very much!!!