Exactly. I'd read it as

> I want to correct errors that the DB wizard who implemented SQLite chose not to

When there's a design decision in such a high profile project that you disagree with, it's either

1. You don't understand why it was done like this.

2. You can (and probably will) submit a change that would solve it.

If you find yourself in the situation of understanding, yet not doing anything about it, you're the Schrodinger's developer: you're right and wrong until you collapse the mouth function by putting money on it.

It's very rarely an easy to fix mistake.

> 2. You can (and probably will) submit a change that would solve it.

SQLite is not open to contribution - https://www.sqlite.org/copyright.html

> 1. You don't understand why it was done like this.

sure, I would like to understand it. That's why the post!