TYPO3 Core

"While this might sound like a special case of database inconsistency, it actually seems to be the default case when upgrading from 6.0 or 6.1"

Did you run the migration wizards? Course this shouldn't be the case if you upgrade from 6.0/6.1.

Updating TYPO3 before 6.0 had an issue, which was solved today with #46020.

The issue behind the auto creation with empty values is #57545. I would like to concentrate me on your upgrade problem in this issue.

Yep, I ran the migration wizards. One step stated the splitting and creation of FAL stuff, so I didn't skip on that.
Actually, the sys_file_metadata table seemed to be completely populated with records, but they were empty except for the references to sys_file

Thanks for help, hopefully I have time tomorrow to take a look. The SQL snippet seams to be correct.

Hi Bernhard,

I couldn't reproduce this issue, so I need some more information:

Dump of the SQL Structure of the sys_file before migration.
Dump of the SQL Structure of the sys_file_metadata after migration.

The FileTableSplittingUpdate wizard takes all data from sys_file and inserts them into sys_file_metadata in one SQL Statement. I don't think that there is an error, but maybe the table structure has issues.

One possibility in my mind, did you start the "Database analyzer" before migration?

I've tested this again with 6.2.3 including running the complete set of install tool upgrade wizards and scheduler tasks and there seem to be no further problems regarding image dimensions.