Hmm, that's a new one for me. If you look at dbscripts/xml/ojs_schema.xml, you'll see...
- Code: Select all
CREATE INDEX article_settings_name_value ON article_settings (setting_name, setting_value);
That's the line that's causing problems. It's creating a database index on the article_settings table, and the error message is reporting that the content is too long.
I remember having a recent conversation about this with one of the developers but can't remember the outcome -- I believe we were planning to switch to a hash for queries but haven't done so yet.
That query is only used for a few public identifier queries so you're safe to remove those three lines for now, restore from backup, and run the upgrade script again. If you encounter performance problems when using public identifiers, post here again and we'll look for solutions. Once we move to a hash implementation a subsequent upgrade will resolve it automatically when you upgrade.
Public Knowledge Project Team