Changing the language shouldn't require the deletion of the whole database.

Seshat supports multiple languages. If the language is changed after the index has been created opening the index would result in an error.

To support language changes the index would need to be deleted while the database can be kept, the events in the database should also be re-indexed with the newly re-created index.

Start by tracing how the existing index is opened and how its language is stored or validated. Confirm that changing the language can preserve the database, recreate only the index, and re-index the events with the new language. Done means opening an index after a language change succeeds without deleting the database.

Written by the indexing model from the issue text.