> 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.
> In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches. If you would like to suggest a change and you include a patch as a proof-of-concept, that would be great. However, please do not be offended if we rewrite your patch from scratch.
> 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.