You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2024. It is now read-only.
Hi @nickbe. Yes, love the idea. That is on the list of features to add. Though I'm not sure when I'll be able to implement it yet. I'm assuming a good idea would be to create a config variable, like index and you can define an array of fields. Then the first time it runs it builds the index, and then any updates/deletes would have to rebuild indexes, or clear them out and then rebuild the index on the next query.
AFAIK, create index is to avoid scanning all documents to display the results.
I think to create index will be hard to implement because basically an array will loop from the first until the end and right now, the design of this project seems not possible.
Yes maybe there is another way but it may refactor the whole design of this project.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would it be possible to implement some sort of index mechanism?
This way queries which refer to indexed fields would be found much faster.
The text was updated successfully, but these errors were encountered: