Register multiple IModels via RegisterInContainer

[timvandesteeg]

I'm currently working on a POC to implement a single GraphQL service for multiple microservices. However, I can't seem to use more than one IModel via RegisterInContainer. Looking at the code (my complements on the high quality btw!), I see only the last one is actually used. Is it technically possible to allow multiple DbContexts to be used within the same service?

Or would you suggest to use one GraphQL endpoint per microservice?
Or create one additional DbContext that contains all entities in it's IModel and use that one instead?

Thanks :)

[timvandesteeg]

var builder = new DbContextOptionsBuilder();
builder.UseSqlServer("fake");
using (var context = new DbContext(builder.Options))
{
    ModelBuilder modelBuilder = new ModelBuilder(ConventionSet.CreateConventionSet(context));
    modelBuilder.ApplyConfigurationsFromAssembly(typeof(PaymentContext).Assembly);
    modelBuilder.ApplyConfigurationsFromAssembly(typeof(LicenseContext).Assembly);

    EfGraphQLConventions.RegisterInContainer(services, modelBuilder.Model);
}

This seems to work. This approach be easier to implement as generic function, since you only need an instance of the normal DbContext.

[SimonCropp]

want to submit a PR that enables this?

[hnviradiya]

I am also in need of this requirement. Facing same issue. Any workaround?

[SimonCropp]

@hnviradiya @timvandesteeg so i can better understand your use case, can you point me to where your open source projects are hosted?

[Shitikyan]

I have the similar issue, when registering multiple DbContext from same assembly. It comes from
EfGraphQLService's includeAppender when try to resolve the registered items, because EfGraphQLService is registered as Singleton and it just saves the only one Dictionary<Type, List> navigations

[Shitikyan]

This is the sample repo
https://github.com/Shitikyan/GraphQL.EF.Sample

[SimonCropp]

@timvandesteeg @hnviradiya @Shitikyan just to confirm you all read this https://github.com/SimonCropp/GraphQL.EntityFramework#community-backed

This project relies on financial contributions from the community to ensure its long term viability. It is expected that all developers become a Patron on OpenCollective.

[hnviradiya]

so as this is not going to be supported. I will have to remove IQueryable support from project. 2-3 more round trips will be there. But that will be fine.

[SimonCropp]

@hnviradiya i didnt say it wouldnt be supported. PRs may still be considered. But this project takes a non trivial amount of time to maintain, and i am likely to focus on requirements i need rather than what people are asking me to code for them in my free time. all this is pretty clearly explained here https://github.com/SimonCropp/GraphQL.EntityFramework/blob/master/pages/licensing-patron-faq.md

[SimonCropp]

this has been fixed in version 6. see the upgrade guide https://github.com/SimonCropp/GraphQL.EntityFramework/blob/master/doco/upgrade-guide-5to6.md

[SimonCropp]

doco: https://github.com/SimonCropp/GraphQL.EntityFramework/blob/master/doco/configuration.md#multiple-dbcontexts