Primary key in file_managed_data

Confirmed! Only seems to happen with Gutenberg installed. See /admin/reports/status

Interesting. The whole table seems to be related to the build-in media library that comes with the Gutenberg module and is only used, when the "Media Library" from Core is not installed.

We should add the primary key as long keep the feature.

Here's a patch. Please keep in mind that applying patches with hook_update_N to real world applications are risky, because there is the chance that another patch with an update function gets committed first.

Simple change, patch works, not much more to say here. Would be great to get it merged soon to avoid hook_update_N issue mentioned by @szeidler.

Updated the default gutenberg_schema() entry so that new module installs should have the fid as the primary key, and created a PR for it.

Just needs review/testing from @szeidler, and he can merge it in.

Good and important catch @codebymikey.

Looks good!

Merging the change in. Thanks for your contributions.

Automatically closed - issue fixed for 2 weeks with no activity.

I think this patch may have unintended consequences. Today I upgraded from D9 to D10. When I attempted to run database updates, I was stuck on this patch. I do not have a table file_managed_data, only files_managed. I was able to move past this by duplicating files_managed as files_managed_data. After the migration, I tested my content, and no files/data are being inserted into file_managed_data, so I just removed the unnecessary file_managed_data table.

We could of course have added a table exist check on the update hook, but I'm just surprised that the table does not exist for your since it's defined as hook_schema + was added as an update hook for existing sites years ago.
Do you know since when the site has been using Gutenberg? Have you been an early adopter?