Hacker News Reader

For me an important caveat is the typing. With all respect for the original author of SQLite -- he has done an outstanding job-- I think he underestimates the value of a good typing system. I have seen some databases that had all kinds of messy data. Back in the day MySQL was also quite loose with regards to checking data. Undoing the damage is in most cases not possible. For a business data is more important than code, so be strict up front.

I know, SQLite has added the option to enforce type checking. The authors still don´t believe in the value of it and the available types are quite limited and thus loose. I think this is something that pgsql got quite right, where you can have your domain types on the database level.

On the other hand, if you keep this as a replacement for your config file ( I thought this was the original purpose?), then yeah, you get an awesome deal. I wouldn't dare to build my business on it, just like I don´t believe in MongoDb and any untyped language for serious purposes.

View on HN

sqlite> create table t ( id integer primary key, n integer check ( typeof( n ) = 'integer' ) ); sqlite> insert into t ( n ) values ( 1 ); sqlite> insert into t ( n ) values ( '1' ); sqlite> insert into t ( n ) values ( true ); sqlite> insert into t ( n ) values ( 'x' ); Runtime error: CHECK constraint failed: typeof( n ) = 'integer' (19) sqlite> select * from t; ┌────┬───┐ │ id │ n │ ├────┼───┤ │ 1 │ 1 │ │ 2 │ 1 │ │ 3 │ 1 │ └────┴───┘ sqlite> select ( select n from t where id = 1 ) = ( select n from t where id = 2 ); 1 // i.e. true