SQLite 3.8.0 Release with next-generation query planner

Re:SQLite 3.8.0 Release with next-generation query planner by dnr on Monday August 26, 2013 @09:17PM (#6280883)

SQLite isn't a replacement for postgresql (or vice versa). SQLite is a replacement for fopen.

Among its many advantages in that situation: a database is contained in a single file with minimal overhead, the source is shipped as one .c file and encouraged to be statically linked, and the code size is relatively small (compared to something like postgresql).

[ Parent | on HN ]

Re:SQLite 3.8.0 Release with next-generation query planner by mamcx on Monday August 26, 2013 @11:10PM (#6281256)

I hope sqlite someday add functions and/or store procedures. Plus better error messages (like when a foreign key is violated)

[ Parent | on HN ]

Re:SQLite 3.8.0 Release with next-generation query planner by kevingadd on Tuesday August 27, 2013 @03:19AM (#6281972)

Why exactly do you need stored procedures in sqlite? You can just write code. Are you using it in a scenario where you can't write code to interact with sqlite?

[ Parent | on HN ]

Re:SQLite 3.8.0 Release with next-generation query planner by mamcx on Saturday August 31, 2013 @09:11PM (#6308707)

For the same reason are used in others DBs.

Some things are better expressed in the DB native language. Help to abstract and share implementation of DBs that are used by different languages.

[ Parent | on HN ]