wicked cave
Hi ! Is there a way to use a dynamic name based on the request for the TypeOrmModule when using useFactory ?
Reference : https://docs.nestjs.com/techniques/database#multiple-databases
In the documentation and the type definition it don't seems to be possible..
dusk moss
Nope, nor does there really need to be. You only inject one connection at a time to your application, regardless of the connection's details, so having a single provider token for the connection is fine
wicked cave
Nope, nor does there really need to be. You only inject one connection at a time...
But if my connection is create from the request ? I want a tenancy connection depending of the request. Is this possible without the dynamic name ?
dusk moss
The connection can be created from the request, for each request, but the injection token, what tells Nest what to inject and where, will be static. The value the token points to is dynamic, but the token itself is static
wicked cave
The connection can be created from the request, for each request, but the inject...
So there is no tenancy connection if the connection is re-created on each request ? Do you have an example please ? 😊
dusk moss
Usually, yes. It's recreated. There is the idea of durable providers which are request scoped and reused
wicked cave
Usually, yes. It's recreated. There is the idea of durable providers which are r...
Is there a problem with recreting the connection on each request ? Does that affect performance by a lot ?
dusk moss
Benchmark it and find the performance difference
wicked cave
Benchmark it and find the performance difference
Is this possible to use a durable provider with the TypreormModule ? thanks!
dusk moss
Should be. That was one of the use cases in mind
wicked cave
Sorry to bother you with this, but do you have an example ? Even without typeorm. The one in the documentation doesn't help me to understand how to use a durable provider from a module defined in the "import" of a module. 😅
dusk moss
I don't but check the integration tests