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

Improve SQL performance by not forcing sentDate #381

Open
guusdk opened this issue Mar 21, 2024 · 0 comments
Open

Improve SQL performance by not forcing sentDate #381

guusdk opened this issue Mar 21, 2024 · 0 comments

Comments

@guusdk
Copy link
Member

guusdk commented Mar 21, 2024

When a message query is performed without a date range, the existing implementation uses epoch and 'now' to define a range. This effectively covers every message in the archive, and thus should be benign.

Using an explicit data range does require the database to evaluate these values, which can result in sub-optimal performance.

The plugin should be modified to no longer explicitly use epoch and now when no data range is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant