5 ms·

Is SQLite used as the internal database for some popular systems?

by whitten 12y ago

petilon 12y ago
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/conceptual/CoreData/Articles/cdPersistentStores.html https://developer.apple.com/library/mac/documentation/cocoa/... http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html http://developer.android.com/reference/android/database/sqli...
dangoor 12y ago
Firefox and Chrome both use SQLite for some of their data. It's a great package.
- rplnt 12y ago
  Opera did too, also the new one does.
qewrffewqwfqew 12y ago
In case you've been living under a rock .. https://www.sqlite.org/mostdeployed.html https://www.sqlite.org/mostdeployed.html
- erikb 12y ago
  Your choice of languages leaves room for improvement.
- Zecc 12y ago
  That text needs an update. There's no mention of Android and Symbian is all but dead.
cwt137 12y ago
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 http://twit.tv/show/floss-weekly/26
rectangletangle 12y ago
It comes bundled with most Python implementations (import sqlite3).
mathnode 12y ago
http://www.sqlite.org/famous.html http://www.sqlite.org/famous.html
petercooper 12y ago
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.
rakoo 12y ago
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 http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki
- 72deluxe 12y ago
  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.
  - stsp 12y ago
    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 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.
e40 12y ago
Adobe Lightroom.
KC8ZKF 12y ago
iTunes
brucehart 12y ago
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.

Is SQLite used as the internal database for some popular systems?

by whitten 12y ago

Is SQLite used as the internal database for some popular systems?

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/conceptual/CoreData/Articles/cdPersistentStores.html https://developer.apple.com/library/mac/documentation/cocoa/... http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html http://developer.android.com/reference/android/database/sqli...

dangoor 12y ago

Firefox and Chrome both use SQLite for some of their data. It's a great package.

rplnt 12y ago
Opera did too, also the new one does.

qewrffewqwfqew 12y ago

In case you've been living under a rock .. https://www.sqlite.org/mostdeployed.html https://www.sqlite.org/mostdeployed.html

erikb 12y ago
Your choice of languages leaves room for improvement.
Zecc 12y ago
That text needs an update. There's no mention of Android and Symbian is all but dead.

cwt137 12y ago

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 http://twit.tv/show/floss-weekly/26

rectangletangle 12y ago

It comes bundled with most Python implementations (import sqlite3).

mathnode 12y ago

http://www.sqlite.org/famous.html http://www.sqlite.org/famous.html

petercooper 12y ago

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.

rakoo 12y ago

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 http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki

72deluxe 12y ago
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.
- stsp 12y ago
  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 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.

e40 12y ago

Adobe Lightroom.

KC8ZKF 12y ago

iTunes

brucehart 12y ago

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.