
When performing the old style `CREATE TABLE ... AS SELECT ...` (CTAS) statement, no indexes are added. In addition, rowid is not added. Even if manually specifying an autoincrement column in the original schema, this autoincrement column does not get recreated with the CTAS statement. So instead, this change reuses the original `CREATE TABLE` statement which explicitly defines all of the relevant columns. In addition, it explicitly adds an autoincrement integer primary key. This has the same semantics as the existing implicit `rowid` column that sqlite creates. From from https://sqlite.org/autoinc.html: > In SQLite, a column with type INTEGER PRIMARY KEY is an alias for the ROWID > (except in WITHOUT ROWID tables) which is always a 64-bit signed integer. However, as it is explicit now, is copied when doing the `INSERT INTO ... SELECT ...` statement to get data from the real table to the temp table in preperation for updates (and back again after the update has populated the temp table). Note that this makes the `INSERT INTO ... SELECT ...` statements slightly more brittle, because now we need the table definition used to create the temp table (from `DBHelper.CREATE_APP_TABLE`) to have the same column order as those in the real `fdroid_app` table. While this may sound like a silly comment to make, it is important because database migrations can result in a database having the correct set of columns, but in a different order to how they were specified in the original create table statement. If a database migration performs an `ALTER TABLE ... ADD COLUMN ...` the column will be added at the end. If at the same time the `CREATE TABLE` is changed so that the new column is specified as the second to last column in the list of columns, then the `INSERT INTO ... SELECT ...` will not work as expected.
F-Droid Client
Client for F-Droid, the Free Software repository system for Android.
Building with Gradle
./gradlew assembleRelease
Direct download
You can download the application directly from our site or browse it in the repo.
Contributing
See our Contributing doc for information on how to report issues, translate the app into your language or help with development.
IRC
We are on #fdroid
and #fdroid-dev
on Freenode. We hold weekly dev meetings
on #fdroid-dev
on Tuesdays at 20h UTC, which usually last half an hour.
FAQ
- Why does F-Droid require "Unknown Sources" to install apps by default?
Because a regular Android app cannot act as a package manager on its own. To do so, it would require system privileges (see below), similar to what Google Play does.
- Can I avoid enabling "Unknown Sources" by installing F-Droid as a privileged system app?
This used to be the case, but no longer is. Now the Privileged Extension is the one that should be placed in the system. It can be bundled with a ROM or installed via a zip, or alternatively F-Droid can install it as a system app using root.
License
This program is Free Software: You can use, study share and improve it at your will. Specifically you can redistribute and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Some icons are made by Picol, Icomoon or Dave Gandy from Flaticon or by Google and are licensed by Creative Commons BY 3.0.
Other icons are from the Material Design Icon set released under an Attribution 4.0 International license.