Keep schema commit from deleting NULL-generation artifacts
The migration function has the replacement-exists guard, but the schema snapshot still deletes any artifact row whose typed index_generation_id is NULL. Fresh schema rebuilds will therefore drop rows written by the current workers, which still populate the generation in metadata for artifact tables like document_images, immediately removing images and other enrichment artifacts during commit_document_index_generation.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #134 (comment)
The migration function has the replacement-exists guard, but the schema snapshot still deletes any artifact row whose typed
index_generation_idisNULL. Fresh schema rebuilds will therefore drop rows written by the current workers, which still populate the generation inmetadatafor artifact tables likedocument_images, immediately removing images and other enrichment artifacts duringcommit_document_index_generation.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #134 (comment)