When installing a module, either during initial install of Drupal or later, the schema version at that point gets stored in the schema_version field in the system table.

As installation profiles are considered modules these days, hook_update_N() can be used in profiles, but the schema version for a profile doesn't get determined nor stored.

I guess this is a bug, but I haven't had time to find out yet where to fix that.

CommentFileSizeAuthor
#3 schemaVersion.png13.38 KBnicxvan

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
nicxvan’s picture

nicxvan commented

This is fixed in 11.x I just confirmed that update hooks in profiles only run once and the schema is stored in the db.

I am testing a Drupal 7 site to see if it is an issue there.

nicxvan’s picture

nicxvan commented
Status: Active » Closed (cannot reproduce)
StatusFileSize
new schemaVersion.png13.38 KB

I just checked, the schema does get stored, see screenshot.
I also confirmed the update hook only runs once.