Add not null constraint to noteable_type
noteable_type is already validated for prescene in the application code and this commit adds the corresponding DB constraint to prevent invalid notes records. It also contains a migration to create an index asynchronously that will be used to locate, backup and remove the notes records with null noteable_type for .com. Changelog: other
显示
- db/migrate/20240206085539_add_not_null_constraint_to_notes_noteable_type.rb 14 个添加, 0 个删除...6085539_add_not_null_constraint_to_notes_noteable_type.rb
- db/post_migrate/20240206093635_add_index_to_notes_where_noteable_type_is_null_async.rb 16 个添加, 0 个删除...5_add_index_to_notes_where_noteable_type_is_null_async.rb
- db/schema_migrations/20240206085539 1 个添加, 0 个删除db/schema_migrations/20240206085539
- db/schema_migrations/20240206093635 1 个添加, 0 个删除db/schema_migrations/20240206093635
- db/structure.sql 3 个添加, 0 个删除db/structure.sql
- spec/lib/gitlab/markdown_cache/active_record/extension_spec.rb 1 个添加, 0 个删除...lib/gitlab/markdown_cache/active_record/extension_spec.rb
加载中
想要评论请 注册 或 登录