Dear Maintainer,

Using sqlalchemy's reflection feature will result in an incomplete definition
of computed/generated columns (those using "GENERATED ALWAYS AS") in sqlite if
the expression includes a function call (e.g., INSTR()).

I reported this to sqlalchemy thinking is was a user error, but ended up being
a bug.  A fix has been developed, but not yet released for either 1.4 or 2.0.

If the patch could be brought in for either, I would be appreciative, but
understand if not.  At the least, it would be good for 2.0 I think.

Upstream report:
https://github.com/sqlalchemy/sqlalchemy/discussions/11580

Upstream bug:
https://github.com/sqlalchemy/sqlalchemy/issues/11582

Upstream patch:
https://github.com/sqlalchemy/sqlalchemy/issues/11582#issuecomment-2212392525

Hmm... I just noticed that the submitted patch for the 2_0 branch has the
changelog entry in the "unreleased_14" directory.  I suppose you all are the
experts are sqlalchemy stuff and would know if this is working-as-intended or
not.

(I suppose I cheated in "including a patch" by pointing to an existing one.)

Thanks,
mrc