TYPO3 Core

Urs answered by mail instead of posting here:

Hello Helmut

Yes, cached were flushed, as i remember me. But now, I can’t revalidate it, because i am using an other environment now.

Kind Regards
Urs

As I wondered which line the report referred to, I want to share what I've found (the issue can be kept closed, but in case we reencounter that error this might be of help):

The issue was reported between v12.0 and v12.1 release, that means it refers to v12.0 state, where line 683 assumes every SchemaDiff has to return at least one statement:
https://github.com/TYPO3/typo3/blob/v12.0.0/typo3/sysext/core/Classes/Database/Schema/ConnectionMigrator.php#L683

This code has been refactored in main/v13:
https://github.com/TYPO3/typo3/blob/edd03d462ea3cb26d6e70c9fbc1dd00ef6c0ec0e/typo3/sysext/core/Classes/Database/Schema/ConnectionMigrator.php#L894-L899
would still be interesting to know, how this case was produced and if v13 could end up with an empty SQL statement as well.
Sure, it will not produce the `null` error, but something seems to have been odd (and cache flushing can not be the reason, as cached are package-dependant and ext_tables.sql)

Another minor aspect: The extension has multiple CREATE TABLE statements for tt_content (shouldn't be an issue, but maybe that was the trigger?)
https://bitbucket.org/maagit/maagitblog/src/d8bcb547738750d471838313ec836dd3911f0592/ext_tables.sql?at=v13.4.0#lines-27:40