The _int handling is applied to all revision fields during system_update_8400()

Problem/Motivation

The upgrade from 8.2 to 8.3 is supposed to created revision_user and revision_created fields on the block_content_field_revision table (via block_content_update_8003()). After the update however, with dynamic_entity_reference enabled, there are only _int versions of those fields:

mysql> describe block_content_field_revision;
+-------------------------------+------------------+------+-----+---------+-------+
| Field                         | Type             | Null | Key | Default | Extra |
+-------------------------------+------------------+------+-----+---------+-------+
| id                            | int(10) unsigned | NO   | MUL | NULL    |       |
| revision_id                   | int(10) unsigned | NO   | PRI | NULL    |       |
| langcode                      | varchar(12)      | NO   | PRI | NULL    |       |
| info                          | varchar(255)     | YES  |     | NULL    |       |
| changed                       | int(11)          | YES  |     | NULL    |       |
| revision_translation_affected | tinyint(4)       | YES  |     | NULL    |       |
| default_langcode              | tinyint(4)       | NO   |     | NULL    |       |
| revision_created_int          | int(10) unsigned | YES  |     | NULL    |       |
| revision_user_int             | int(10) unsigned | YES  |     | NULL    |       |
+-------------------------------+------------------+------+-----+---------+-------+

Those _int fields are most likely coming from this module, but I have no idea a) why it doesn't create the normal fields too, and b) why it's doing so for a non-entity-reference field (the revision_created field).

There's this possibly related core issue too: #2865702: Revert schema version when update process failed..

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes