Okay, but how does it handles indexing and query. Suppose we have a large database, what are the performance tradeoffs ? First you will do an SQL search to load data into Swirl ? Or is there something different?
We currently use Spacy Large English Core Model, we've experimented w/ others. We can store our meta data in many of the DBs supported by Django. We have a number of deployments on Postgres. We can also support Searching SQL DBs Using a flexible query template.
If you mean connecting to various databases as content sources to search, yes, Swirl can do that (e.g. PostgreSQL as a source, etc.). Does that help?