News for hackers. Stuff that matters.

A comment on Why you should probably be using SQLite. Parent comment

Re:Why you should probably be using SQLite by Timon3 on Friday October 27, 2023 @08:57AM (#38037814)
> Also, column types are not checked and you can easily insert a string into numeric column.

This is only true if you don't use strict tables (implemented end of 2021): https://www.sqlite.org/stricttables.html

If you define a table as strict, the data is coerced, and if not successful an error is thrown.

[ Parent | on HN ]
Re:Why you should probably be using SQLite by mickeyp on Friday October 27, 2023 @11:56AM (#38040187)
> If you define a table as strict, the data is coerced, and if not successful an error is thrown.

Coercing the data is hardly better. Now you have data integrity issues and you have no errors!

[ Parent | on HN ]
Re:Why you should probably be using SQLite by Sammi on Tuesday October 31, 2023 @11:22AM (#38086223)
SQLite attempts to coerce the data into the appropriate type using the usual affinity rules, as PostgreSQL, MySQL, SQL Server, and Oracle all do. If the value cannot be losslessly converted in the specified datatype, then an SQLITE_CONSTRAINT_DATATYPE error is raised.

https://www.sqlite.org/stricttables.html

[ Parent | on HN ]
Re:Why you should probably be using SQLite by IshKebab on Friday October 27, 2023 @04:04PM (#38043247)
> the data is coerced

Seriously? And there I was thinking they actually fixed this mistake... they just made another schoolboy error.

[ Parent | on HN ]
Re:Why you should probably be using SQLite by Mawr on Saturday October 28, 2023 @01:30AM (#38047414)
To clarify the bit about coercion: "SQLite attempts to coerce the data into the appropriate type using the usual affinity rules, as PostgreSQL, MySQL, SQL Server, and Oracle all do."
[ Parent | on HN ]