GitLab

Move HAVE_POSIX_FALLOCATE into Android.mk, rather than assigning
this in sqlite3.c. This customization was added in
1eb051da.

Remove an unnecessary whitespace difference.

Change-Id: Id4d6c48b59983ebb4c7160ca364d247febb4e543

This sanitizes deleted data by overwriting it with zeroes, rather than
having it persist within SQLite's free list. In some cases, the data may
end up persisting on the underlying storage due to wear levelling but
only a process with direct access to block devices would be able to
access it.

This can be disabled via `PRAGMA SECURE_DELETE = 0;` for niches where
deletion throughput is more important than enhanced privacy. The
performance impact is very small unless large strings and blobs are
being deleted. Android itself doesn't have any uses where disabling it
would make sense, and very few apps will be negatively impacted. As a
data point, Chromium and Firefox already use this for their own
databases.

Change-Id: I07f0e1584f0b2405f080198ad7b1f4e7ed7f68fb

- No android specific features or dependencies on android libs.
- Built using the NDK headers for the target.

bug: 26457850
Change-Id: I4014e1c6bf7be9c8f2008f952122f8951e336122

Bug: 23566667
Change-Id: Ia0452d8893d6735ee2c789e96ad4eb67daf1c835

Bug: 21730722
(cherry-picked from commit 55536230)

Change-Id: I25f76ce4794c4ee4caf4c85d35c318dac3b7bac8

Bug: 21730722
Change-Id: I44cfb0d6976ec06366cae8df7a52e1c27c6e7ff2

Downloaded from http://www.sqlite.org/2015/sqlite-amalgamation-3080900.zip

  $ sha256sum sqlite-amalgamation-3080900.zip
  40a9f51a250fc41f6b5053a778681c622d82dec592c85de21edd3640eeb5f093  sqlite-amalgamation-3080900.zip

dist/orig contains the stock sqlite3 code, as packaged in the ZIP file above.

dist contains a copy of dist/orig, but with the Android.patch file applied.
Please see Android.patch for a list of differences between stock and
Android.

No new patches are introduced.

Bug: 20099586
Change-Id: Ic7be6d920698984dee67458678086e88db9a06d3

ICU exports them using LOCAL_EXPORT_C_INCLUDE_DIRS.

bug: 18581021
Change-Id: I98048a4f6a9163fff6d3a71712d8249b2b00d04b

Change-Id: I0b88ae01fced0f44880c30aa303c6828b6cdb821

Bug: 13751317
Change-Id: I64e66eb34dbe10b39ec2e8c37da0038705b4931f

Change-Id: Ibb028f74b6a93fc877d9c207aee26f3b070b12d0

This makes the "icu" tokenizer available for applications to use
with full text search.

Bug: 5465099
Change-Id: I5ad9790ee126d69b68eb3d8907320e74fb89219d

As it will break windows builds.

Change-Id: Ifb58a90b11ce9379b372c038cfb99d418374529d

This will reduce each heap object allocated in sqlite3 by 8 bytes.

BUG: 10625488
Change-Id: I0aba96cd36173717fc40d1b65230266b2d1e4bf8

(cherry picked from commit df821ceb)

Change-Id: Idb0599afd6d93428225c855c1c197a6871b49a07

Change-Id: I4c01f3f32b0dbe450206f3e8cbf3d4eedfdb6562

Bug: 8580410
Change-Id: Icc11edb1f7f684c8a72d0c0ef3d696b7a0883947

This change improves performance on certain kinds of transactions
such as UPDATEs by allowing SQLite to make stronger assumptions
about data integrity on the disk.

The powersafe overwrite assumption demands that when a byte is
written to a file and a power event occurs then the only bytes
that may have been modified are the ones that were being written.

In absense of the powersafe overwrite assumption, SQLite assumes
that a write of any range of bytes within a disk sector may
potentially cause the rest of the sector to be corrupted.  SQLite
needs to do extra work to compensate for this problem, which adds
overhead to certain transactions.

On flash devices, writing a byte causes the sector to be rewritten
somewhere else on the device.  Eventually the old sector may be
erased and reused.  The powersafe overwrite assumption therefore
holds as long as the flash device never leaves behind (observable)
half-written sectors in case of a power event.  This is a fairly
safe assumption to make.  Some flash devices apparently include
measures to ensure that the last write fully completes when
power is interrupted.  In any case, the window of opportunity
for corruption to occur is very small.

Bug: 6484633
Change-Id: I0b0ef664b3a2a0e85c6099f0130d0affc5562be5

Previous to this, the temporary journal files created by sqlite
were globally readable, leading to the possible leakage of
sensitive data (CVE-2011-3901).

Bug: 6222215
Change-Id: I29a85c9077c622b038e7fb190c3d7833b924df99

Previous to this, the temporary journal files created by sqlite
were globally readable, leading to the possible leakage of
sensitive data (CVE-2011-3901).

Bug: 6222215
Change-Id: I29a85c9077c622b038e7fb190c3d7833b924df99

Linux has a working fdatasync() so we should use it!
This change alone improves performance by around 20% by reducing
the number of synchronous I/O writes of irrelevant metadata
changes.

Change-Id: Iebe0c32a7e018ec0ced2347b7d62b2b7dc5aa376

It seems some people really are depending on the $1 syntax
to bind variables.  Ok.

Bug: 5926203
Change-Id: Iae0cc6a0882b536fb5f3cdad687a6d7b41843d9f

Turn off stuff we don't need.
Enable FTS4.
Enable ICU tokenizer.

Bug: 5530406
Bug: 5465099
Change-Id: Idcc52050a4d048a64bfe8484e419dc8d2b27d6ed

Ported all original Android-specific patches.

Change-Id: I2c5801a92d783e2c5cba72147d9fb777ad7c8443

Using pread64 instead of lseek/read makes half the syscalls. Would you
like some free performance?

Change-Id: I2942adc18878ae80b41862aba945cd50e285bb95

Bug: 5010576

Change-Id: Ided77f7e44149b71ec74e24e42da7df0bd5fae2e

Change-Id: Ibeaa5ca225d1acc069fa391fbf68c5ae5ae5613f

Change-Id: I5e7a1b78914ee5c2affe64c24eb90a280ee83f0f

Change-Id: Icf977dc9c167ca1934c2058a681cea3bd9b1d95d
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>

The media provider is now using the emulated /mnt/sdcard file system,
so this change is no longer necessary.

This reverts commit 439e88e7.

Change-Id: Ied12275767e3a399d7e455ac2102527ccd8b888d

Change-Id: I8a3f620cd6633f2be47ac05e17ea642f00b71e91
Signed-off-by: Mike Lockwood <lockwood@android.com>

Change-Id: I900daf7f205f8f666eac9c4070d2e5c99d85b3b3

Change-Id: I385f18c4cc4386bbb76616723a5bc80e7b8e07cd

is there any reason why the sqlite3 command line tool on device
should not have android functions and collators

Change-Id: I86fc12c9c74b49a20c5647abc88c1bffd84591ee

bug:2651952
this mode was previously available in Eclair and below. this mode was removed
by me for no particular reason in Froyo.
this change doesn't bring in any new modules into sqlite. just
allows FTS1 or 2 apps be used with FTS3 running in backward compatibility mode

Change-Id: Id5d72b440a378dd6d6703ce99b5d3d70ffd0c80f

(Merge master Change I4774eac5)

Change-Id: I4774eac53bd28d287a7ef139108ad4ffb9dac2ff

you should notice the following from the Android changes in 3.5.9
1. Android Changes are grouped wherever possible.

To Do
1. sqlite3_get_pager_stats() needs to be completed
2. Android change lines 63480-63482 on master branch in sqlite3.c is
not ported yet. can't see where it goes in 3.6.22 code.

Google gears team implemented a patch to sqlite called "poison the header".
It got included in sqlite android shipped.

This patch is meant to corrupt the database header if some sqlite process
concludes that the database is corrupt. Thereafter, any other sqlite process
opening the same database file would quickly see the corruption and exit.

I am not convinced that this is a useful patch for Android.
And, it patch didn't make it to the open source version of sqlite.

could it be causing previously nonexisting
database corruption, by incorrectly poisoning the database header? thats
what I am suspecting.