From 9e0787ab43fa37fe19566e4f6a9652c06f762d90 Mon Sep 17 00:00:00 2001 From: Oliver Date: Tue, 26 May 2026 07:03:38 +1000 Subject: [PATCH] sqlite limitation docs (#12003) * sqlite limitation docs Ref: https://github.com/inventree/InvenTree/issues/12002 * Fix typo * More typo tweaks --- docs/docs/faq.md | 12 +++++++++++- docs/docs/security.md | 20 ++++++++++---------- 2 files changed, 21 insertions(+), 11 deletions(-) diff --git a/docs/docs/faq.md b/docs/docs/faq.md index 7f2b2c79a0..b0852be612 100644 --- a/docs/docs/faq.md +++ b/docs/docs/faq.md @@ -199,10 +199,20 @@ In either case, ensure that the directory is available *on your local machine* a ## Error Rendering Component -Sometimes, following a software update, you may find that certain components of the web interface are not rendering correctly, and presented with a message similar to the screenshow below: +Sometimes, following a software update, you may find that certain components of the web interface are not rendering correctly, and presented with a message similar to the screenshot below: {{ image("faq/boundary.png", "Error Rendering Component") }} This is often due to a caching issue with your web browser. Try performing a hard refresh of the page to clear the cache, this should resolve the issue in most cases. If the problem persists, refer to the [troubleshooting guide](./troubleshooting.md) for further assistance. + +## Expression tree is too large + +If you are running a large InvenTree deployment on an SQLite database, you may encounter an error similar to: + +``` +Expression tree is too large (maximum depth 1000) +``` + +This is a [known limitation of SQLite](https://www.sqlite.org/limits.html) which can occur when performing complex queries on a large database. Due to [structural limitations](./start/processes.md#sqlite-limitations) of SQLite, it is recommended to use a more robust database backend such as PostgreSQL for larger deployments. diff --git a/docs/docs/security.md b/docs/docs/security.md index d5a34403f5..6a3be12052 100644 --- a/docs/docs/security.md +++ b/docs/docs/security.md @@ -6,24 +6,24 @@ The InvenTree project is committed to providing a secure and safe environment fo To that end, we have implemented a number of security measures over the years, which we will outline in this document. -## Organisational measures +## Organizational Measures The InvenTree project is managed by a small team of developers, who are responsible for the ongoing development and maintenance of the software. Two geographically distributed users have administrative access to the InvenTree codebase. Merges are only done by one of these two users, the maintainer Oliver. Read the Project [Governance](./project/governance.md) document for more information. -InvenTree is open-source, and we welcome contributions from the community. However, all contributions are reviewed and scrutinised before being merged into the codebase. +InvenTree is open-source, and we welcome contributions from the community. However, all contributions are reviewed and scrutinized before being merged into the codebase. ### Security Policy The official [Security Policy]({{ sourcefile("SECURITY.md") }}) is available in the code repository. -We provide this document in our main repo to increase discoverabiltity to ensure that all security issues are handled in a timely manner. +We provide this document in our main repo to increase discoverability to ensure that all security issues are handled in a timely manner. ### Past Reports If we become aware of a security issue, we will take immediate action to address the issue, and will provide a public disclosure of the issue once it has been resolved. We support assigning CVEs to security issues where appropriate. Our [past security advisories can be found here](https://github.com/inventree/InvenTree/security/advisories). -## Technical measures +## Technical Measures -### Code hosting +### Code Hosting The InvenTree project is hosted on GitHub, and we rely on the security measures provided by GitHub to help protect the integrity of the codebase. @@ -35,24 +35,24 @@ Among those are: - (Optional but encouraged) Two-factor authentication for user accounts - (Optional but encouraged) Signed commits / actions -### Code style +### Code Style We enforce style and security checks in our CI/CD pipeline, and we have several automated tests to ensure that the codebase is secure and functional. Checks are run on every pull request, and we require that all checks pass before a pull request can be merged. -### Current versions +### Current Versions InvenTree is built using the Django framework, which has a strong focus on security. We follow best practices for Django development, and we are committed to keeping the codebase up-to-date with the latest security patches and within supported versions. -### Test coverage +### Test Coverage We run coverage tests on our codebase to ensure that we have a high level of test coverage above 90%. This is public and can be found [here](https://app.codecov.io/gh/inventree/InvenTree). -### Pinning dependencies +### Pinning Dependencies We are pinning dependencies to specific versions - aiming for complete reproducibility of builds - wherever possible. Combined with continuous OSV checks, we are able to react quickly to security issues in our dependencies. -## Best practices +## Best Practices We follow most of GitHubs community best practices, check our compliance [here](https://github.com/inventree/InvenTree/community).