3 ms·
> basically spitting on the SQLite projects decision. That is a very emotional response given the SQLite FAQ itself basically admit the design is unfortunate.
by goto11 5y ago
> basically spitting on the SQLite projects decision.
That is a very emotional response given the SQLite FAQ itself basically admit the design is unfortunate. They just state it is too late to change due to backwards compatibility. So it is not crazy to suggest an opt-in flag to change the default behavior, although I can understand if the SQLite team does not bother.
- capableweb 5y agoMaybe the different authors of the website disagrees with each other then, as this paragraph from the website seems to disagree with your statement: > Nevertheless, most other SQL database engines are statically typed and so some people feel that the use of manifest typing is a bug in SQLite. But the authors of SQLite feel very strongly that this is a feature. The use of manifest typing in SQLite is a deliberate design decision which has proven in practice to make SQLite more reliable and easier to use https://www.sqlite.org/different.html https://www.sqlite.org/different.html
- goto11 5y agoTo be clear the FAQ only states it might have been a mistake to make flexible typing the default everywhere, not that support for flexible typing in itself is a bad idea. But I don't think anyone is against support for flexible typing as an opt-in feature.