Skip to content

RerankedIndex handles the DB incorrectly #3

Description

@DrDub

The current implementation either needs two separate SQLite3 DBs (which is inefficient) or will open the same DB twice from different classes (which might lead to blocking each, inefficient and dangerous).

To solve this, add a "DatabaseProvider" interface to Index so that the enclosing class can provide a single open DB to both instances of KeywordIndex and VectorIndex.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions