News for hackers. Stuff that matters.
Re:The SQLite Database File Format by whitten on Monday September 29, 2014 @10:12PM (#8386436)
Is SQLite used as the internal database for some popular systems?
Re:The SQLite Database File Format by petilon on Monday September 29, 2014 @10:20PM (#8386456)
Both iOS and Android use SQLite. That means billions of devices have SQLite on them. That makes SQLite the most popular implementation of SQL. See: https://developer.apple.com/library/mac/documentation/cocoa/... http://developer.android.com/reference/android/database/sqli...
Re:The SQLite Database File Format by qewrffewqwfqew on Tuesday September 30, 2014 @12:52AM (#8386812)
In case you've been living under a rock .. https://www.sqlite.org/mostdeployed.html
Re:The SQLite Database File Format by Zecc on Tuesday September 30, 2014 @05:20AM (#8387359)
That text needs an update. There's no mention of Android and Symbian is all but dead.
Re:The SQLite Database File Format by erikb on Tuesday September 30, 2014 @04:51AM (#8387293)
Your choice of languages leaves room for improvement.
Re:The SQLite Database File Format by dangoor on Monday September 29, 2014 @11:02PM (#8386576)
Firefox and Chrome both use SQLite for some of their data. It's a great package.
Re:The SQLite Database File Format by rplnt on Tuesday September 30, 2014 @10:31AM (#8388323)
Opera did too, also the new one does.
Re:The SQLite Database File Format by mathnode on Tuesday September 30, 2014 @03:58AM (#8387173)
Re:The SQLite Database File Format by cwt137 on Tuesday September 30, 2014 @12:58AM (#8386828)
This podcast talks with the creator about some systems that have SQLite in it and the open source project. http://twit.tv/show/floss-weekly/26
Re:The SQLite Database File Format by rectangletangle on Tuesday September 30, 2014 @01:30AM (#8386886)
It comes bundled with most Python implementations (import sqlite3).
Re:The SQLite Database File Format by petercooper on Tuesday September 30, 2014 @05:22AM (#8387363)
People have provided some good links, but I suspect more Rails apps run on it than you might suspect. I run a few of mine on it. It performs more than well enough until you have tens of people attempting simultaneous writes (or doing crazy stuff like logging or message queuing through SQLite), which perhaps 90%+ of webapps don't need to do anyway. More time is spent rendering the view than grabbing the data in most cases.
Re:The SQLite Database File Format by rakoo on Tuesday September 30, 2014 @08:36AM (#8387789)
Fossil [0] is a scm that does a lot of really useful things that revolve around managing code:

- web interface, native or CGI

- wiki

- bugtracker

Fossil is implemented using SQLite as a storage, which is rather unsurprising given that both are written by the same guy.

[0] http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki

Re:The SQLite Database File Format by 72deluxe on Tuesday September 30, 2014 @09:08AM (#8387909)
That looks really interesting, and lightweight! Have you used it? Any comments on it? I only ask because I have a rather old CVS tree to migrate; I have used SVN but by the looks of things this is even more lightweight. Comments on it would be welcome.
Re:The SQLite Database File Format by stsp on Tuesday September 30, 2014 @09:41AM (#8388060)
Fossil is great. I've been using it increasingly for some of my projects, mostly OpenBSD related where I need versioning before the code moves into CVS. E.g. I used fossil for about a year during the initial development phase of OpenBSD's rtsx(4) card reader driver.

Since fossil has the ability to open a repository (which is a single sqlite database file) in any arbitary directory it nicely overlays with other versioning systems without wanting to store its meta data in hidden directories within the same tree. I often add a bunch of files from /usr/src to a new .fossil file in my home directory for temporary local version control.

You can migrate to fossil from CVS by converting to git first (using e.g. uwe's excellent git-cvs converter at https://github.com/ustuehler/git-cvs), and then generate a git-fast-export stream which you can import into fossil with 'fossil import'. I once tried this with the OpenBSD CVS repository but aborted the import after 7 days. By then it had imported history from 1995 to somewhere in the year 2000, and I was convinced that fossil can't handle trees this large (or histories this deep? Not sure which). This was with a hack to the fossil import code to make it use less sqlite transactions... without that it was even worse (sqlite can handle many queries per second but not so many transactions). So if your code base is large your should consider Subversion or (unless your code base is humongous) git instead.

Re:The SQLite Database File Format by 72deluxe on Wednesday October 01, 2014 @04:21AM (#8393324)
That's great, thanks. I do not have a particularly large codebase so this might be worth a look at!
Re:The SQLite Database File Format by rakoo on Tuesday September 30, 2014 @03:03PM (#8390401)
I haven't used it myself, but the comments I've read are overall similar: it's great to have a single binary to do almost everything you need, making it the ideal choice for projects that have few contributors, little history and/or low SLOC count without having to deploy all the usual jazz.
Re:The SQLite Database File Format by brucehart on Tuesday September 30, 2014 @12:19PM (#8389062)
SQLite is also used in many embedded systems. If you plug in a USB drive to my TV, it creates a SQLite database to keep track of the current position of the video files it plays.
Re:The SQLite Database File Format by e40 on Tuesday September 30, 2014 @11:00AM (#8388512)
Adobe Lightroom.
Re:The SQLite Database File Format by KC8ZKF on Tuesday September 30, 2014 @11:47AM (#8388853)
iTunes