Skip to content

simple search, v1.1a #27

@funderburkjim

Description

@funderburkjim

v1.1a of simple-search is quite different under the hood that v1.1 and previous versions.

It may currently be used with 'simple1.1a' instead of 'simple'.
e.g. https://sanskrit-lexicon.uni-koeln.de/simple1.1a/mw/munih

The performance should be more uniform across words.

The program depends heavily on sqlite fts, which is a full text search (a.k.a. inverted index) capability of sqlite. Making and querying inverted indices underpin most
search applications, but usually (as with those based on java Lucene) require a separate server.
However, sqlite's inverted indexes can be installed and queried much like any other sqlite database.

This functionality (using fts4 version) is available via the version 3.6 of Python at
Cologne. It is not natively available in the sqlite version of PHP at Cologne. However, a PHP
program can query an fts table via python by using 'shell_exec'. That's what is being used
in simple1.1a.

There's a lot more to say, technically, about this approach. But first, use it some and let me
know if any important features have been missed. You can still get at the prior 1.1 version by 'simple'.

Also, as a teaser, try searching for some declined forms (e.g. muniBiH, devena, sisunAm) -- this
is one area where v1.1a might be able to be extended much more readily than prior versions.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions