bug: Document Meltano 2.2.0 requires SQLite >= 3.25.1

As kindly reported by @pdebelak in https://github.com/meltano/meltano/pull/6323#issuecomment-1181955922, the ALTER TABLE table RENAME COLUMN oldname TO newname syntax was introduced to SQLite only in version 3.25.1, and so systems with a default version older than that may fail to run the migration and use Meltano.

[edgarrmondragon]

A better error message or pre-run check for correct sqlite version would be really helpful

This seems like a quick solution by leveraging sqlalchemy.engine.Dialect.server_version_info. We could check the version tuple and fail with a clear message for SQLite<3.25.1. cc @aaronsteers @tayloramurphy

I still think that Meltano should be shipped with the version of SQLite it expects to work with fine out of the box. Adding a dependency on https://pypi.org/project/pysqlite3-binary might be worth exploring, although it’s lacking wheels for macOS and Windows at the moment.

[aroder]

On amazon linux EC2 instance with meltano 2.6.0, I installed pip install pysqlite3 and get version 3.7.* from sqlite3 --version

I followed these instructions to upgrade sqlite version https://developpaper.com/update-sqlite-version-under-centos/

So this confirms everyone else’s findings and hopefully sheds a little light on a path forward