Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Knex cache for each tenant #6

Open
wallacetm opened this issue Jul 10, 2020 · 0 comments
Open

Knex cache for each tenant #6

wallacetm opened this issue Jul 10, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@wallacetm
Copy link
Member

wallacetm commented Jul 10, 2020

Would be great and more performatic if we have a knex cache. This can be a new class or just a map, where the key can be the service_tenant and the value is the knex connection.

And we can create the Multischemase object like this:

Multischemase.Knex('service', 'tenant', ...configOptions);

Without a extra call of setContext('service', 'tenant').

With the knex cache we can solve the pool problem.

@wallacetm wallacetm added the enhancement New feature or request label Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant