DB update results in SQL schema error

Sorry you're haveing trouble @saki_rayogram! I'll try to make some time to dig into this in the next few days.

Based on a quick look, perhaps we should move that schema change to a hook_post_update_NAME() rather than a hook_update_n() based on this change record → .

Note that schema conversions when there is existing data are only supported when executed through a hook_post_update_NAME() implementation, because they need to run in a batch process.

Thanks so much @justcaldwell that would be great!

Hi @saki_rayogram. Sorry for the delay in getting back to this.

I'm still investigating, but in looking back over the history of the module, your issue may stem from the fact that the underlying field type for yearonly was changed from string to list_integer, but there was no upgrade path provided to convert existing data. This occurred with the 8.x-1.3 release. In fact, looks like the issue was previously reported in #2926028: Mismatched entity and/or field definitions → .

Do happen to you know what version of Year Only was originally installed on your site, or do you suspect you were using it prior to the 8.x-1.3 release?

CR: The SQL storage schema for an existing fields can be changed → won't be available until drupal 10.3, but might offer a solution here (?).