3 ms·
> but one that will never be fixed due to backward compatibility I wonder if a fork/"new version" could address this. Like, sqlite2 (v1.0, etc.).
by mastre_ 6y ago
> but one that will never be fixed due to backward compatibility
I wonder if a fork/"new version" could address this. Like, sqlite2 (v1.0, etc.).
- isoprophlex 6y agoConsidering that we're on sqlite3 already, it'd probably be something for the v4 ;)
- deleted 6y ago[deleted]
- warmwaffles 6y agoThere is already an sqlite4 but they haven't done any work with it for a long time.
- mbreese 6y agoThis would be something on the order of the python2 -> python3 transition. Meaning, it would likely take a decade. After going though that, I'm not sure it would be worth it to just change from (default) flexible data types.
- deleted 6y ago[deleted]