[RFC] `sphinx-sql-backend` forked from `atsphinx-sqlite3fts`

[amotl]

Dear @attakei,

first things first: Thanks a stack for conceiving sphinx-sqlite3fts, we absolutely love it. Because you archived the repository at [1], and [2] did not enable issue tracking yet, we have not been able to create a corresponding ticket to get in touch with you over there, so we are doing it hereby.

On this repository, we friendly-forked your code base to explore the feasability to use different search backends. For example, there is a little patch to start adding support for PostgreSQL already (WIP).

• Add backend support for PostgreSQL [WIP] #2

Those changes are not easy to make compatible with the SQLite backend, most prominently it will not be possible to pull off the same trick of embedding the SQLite database into the browser, accessing it through WASM.

So, we guess it is appropriate to durably fork the code base with slightly different goals in mind, because we believe you will never accept corresponding patches, as it would detour from the philosophy of sphinx-sqlite3fts too much. However, if you see a chance to run a hybrid repository, unifying different search backends, please let us know, so that we can adjust our thinking.

Other than this, please also let us know about other ways how we can be supportive for the parent repository you are running over at [2]. Please keep up your excellent work.

With kind regards,
Andreas.

[1] https://github.com/attakei-lab/sphinx-sqlite3fts
[2] https://github.com/atsphinx/sqlite3fts

[amotl]

Thank you for enabling the issue tracker over at your repository. So, I am taking the chance to defer my request over there.

• [RFC] sphinx-sql-backend forked from atsphinx-sqlite3fts atsphinx/sqlite3fts#1