TYPO3 Core

confirmed. stumbled upon that too, some time ago. i suspect doctrine on that, but did not dig deeper, yet. I'd say that is not super critical, but it would be cool if we could get that up and running again.

Same here. Update 7.6 -> 8.7. Mysql 5.6.19.

https://github.com/drud/ddev/issues/654

So with another database server - Mittwald configured server with 5.6.33 - changing the column definition results in another key(index) definition. No prob here.

  KEY `lookup_string` (`ref_string`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8

  KEY `lookup_string` (`ref_string`(333))
) ENGINE=MyISAM DEFAULT CHARSET=utf8

Mittwald
innodb_large_prefix = OFF
DOMAINFACTORY (error here)
innodb_large_prefix = ON

If I change the table definition to

  KEY `lookup_string` (`ref_string`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;