Improve Migrations managed data

[ajcvickers]

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

---

This an "epic" issue for the theme of improving seed data in migrations. Specific pieces of work will be tracked by linked issues.

Done in 7.0

• Don't depend on change tracking for data seeding #22063

Backlog

• Data Seeding: Generate leaner SQL #9998
• Data Seeding: Add sugar for shadow properties #9999
• Data Seeding: Add support for navigations #10000
• Add seed data support for complex types #31254
• Support data seeding for JSON columns #32017
• Support seeding with stored procedures #28702
• Migrations don't use parameters for data operations #20734
• Log when data seeding needs to recreate a row #21823
• Allow reference data to be pre-loaded into the context #12206
• Further update pipeline improvements for seeding #28339
• Warn when seeding with a 0 key #27871
• Consider more efficient pattern for seed data that will never change #14922
• Stream migration commands #19710
• Generate idempotent SQL for SaveChanges when retrying a commit failure #10119
• Add API to clear all existing seed data #13441

[maimonieli]

Hi ,
composed types data seeding it's a very important issue in our application.
any updates / alternatives ?