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

Option to use schema cache #36

Open
1 task done
Tracked by #12
chris-steele opened this issue Sep 25, 2024 · 0 comments
Open
1 task done
Tracked by #12

Option to use schema cache #36

chris-steele opened this issue Sep 25, 2024 · 0 comments
Labels
enhancement New or additional functionality high priority Should be prioritised over all other issues

Comments

@chris-steele
Copy link
Contributor

chris-steele commented Sep 25, 2024

Feature description

The content and adaptframework modules currently bypass the schema cache for all CRUD ops by using useCache: false. This results in a large amount of redundant schema compilations, significant slow down and inefficiency. Content copy and import suffer significantly.

Proposal

Make useCache an option to allow calling functions to determine if the cache should be used or bypassed. If useCache is not specified then the cache will be bypassed by default.

N.B. this proposal affects multiple modules, but for now the issue is defined here.

See also: #41

Can you work on this feature?

  • I can contribute
@chris-steele chris-steele added the enhancement New or additional functionality label Sep 25, 2024
@chris-steele chris-steele added the high priority Should be prioritised over all other issues label Sep 25, 2024
@chris-steele chris-steele changed the title Do not bypass schema cache Option to use schema cache Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New or additional functionality high priority Should be prioritised over all other issues
Projects
Development

No branches or pull requests

1 participant