[Enhancement] Multiple Mutations - Multiple Create

[severussundar]

Nested Mutation refers to the ability to perform mutation operations such as insert, update, and delete on a related entity in addition to the parent entity.

Related items

Preview Give feedback

1. Multi-directional relationships will cause the runtime to fail when building the schema #906
   cosmos graphql mssql pgsql mysql needs discussion +4
   
2. Add capability to modify the linking table even if it is not exposed to satisfy foreign key constraints #285
   enhancement move-to-close mssql pgsql mysql +3
   
3. [Known Issue] Mutations not correctly created for many-to-many relationship #479
   graphql improvement known-issue +3
   

Tasks

Preview Give feedback

1. Schema Generation - Nested Inserts #1698
   Multiple mutations graphql +2
   
2. Evaluate the rollout mechanism of nested mutations #1701
   Multiple mutations graphql +2
   
3. GraphQL Mutation Request Validations - Nested Inserts #1889
   Multiple mutations graphql +2
   
4. AuthZ validation - Nested inserts #1700
   Multiple mutations graphql +2
   
5. Database Query Generation Design Doc - Multiple Create #1887
   Multiple mutations graphql +2
   
6. Multiple Create - Database Query Generation and Selection Set Resolution #1699
   Multiple mutations graphql +2
   
7. Add support for enabling nested mutation from CLI #1950
   Multiple mutations cli graphql +3
   
8. Separate engine workflow depending on whether nested mutations are on/off #1951
   Multiple mutations engine graphql +3
   
9. Multiple Create: Determine and add telemetry to get insights for the feature usage #2022
   Multiple mutations graphql +2
   

   
10. Multiple Create: Feature documentation #2024
    Multiple mutations documentation graphql +3
    

    
11. Nested Create: Finalizing the release plan #2025
    Multiple mutations graphql +2
    
12. Determine order of insertion for relationships: Database Vs Config #2018
    Multiple mutations graphql +2
    
13. Nested Create: Integration/Unit testing #2026
    Multiple mutations graphql test +3
    
14. Need to update relationships data after inferring info from the database #1948
    Multiple mutations bug +2
    
15. Multiple relationships between same source and target entities #1930
    Multiple mutations bug +2
    
16. Multiple Create: Identify and document the limitations and breaking changes. #2023
    Multiple mutations documentation +2
    

    
17. Evaluate if refactor of CreateMutation.Build() to accept RuntimeConfig object is beneficial #2132
    Multiple mutations refactor +2
    
18. Support multiple create mutation for self-referencing relationships. #2157
    Multiple mutations +1
19. Enhance logic for determining the referencing entity when fields backed by a column with default value is present. #2148
    Multiple mutations +1
    

[seantleonard]

removing milestone as individual items are tracked on per-milestone basis.

[JerryNixon]

Done with this workstream. Individual items remain open.