{"push_id":941821902,"size":5,"distinct_size":5,"ref":"refs/heads/cm-13.0","head":"9f0e55a2edff5041a6796d1563b8a2099fd91e38","before":"24a47a6976128bbfc755523a5e170b4110c0cadc","commits":[{"sha":"93ebe8be99404b399592919d6ca55dba34666509","author":{"email":"a80442ec458551709d3e09f515c0c8ee6cebebf5@codeaurora.org","name":"Kiran Kumar H N"},"message":"SQLite: Enable fdatasync for SQLite\n\nSQLite library recommends usage of fdatasync when available.\nSince it is available for linux, enable it. This gives better\nperformance compared to fsync.\n\nChange-Id: I47d5fb9cb1e8331729b54d77f10f7499e028269d","distinct":true,"url":"https://api.github.com/repos/NuclearCM/android_external_sqlite/commits/93ebe8be99404b399592919d6ca55dba34666509"},{"sha":"6ca51ae56fb003a16c0296669e8e9f7c59298cb7","author":{"email":"7662eda885d44e77a928581610e3a6d22accb87e@gmail.com","name":"Park Ju Hyung"},"message":"Upgrade to SQLite 3.9.2\n\nDownloaded from http://www.sqlite.org/2015/sqlite-amalgamation-3090200.zip\n\nSigned-off-by: Park Ju Hyung <qkrwngud825@gmail.com>","distinct":true,"url":"https://api.github.com/repos/NuclearCM/android_external_sqlite/commits/6ca51ae56fb003a16c0296669e8e9f7c59298cb7"},{"sha":"e6290514cfaa411ee82f4f0583ba34bf9eaa3c42","author":{"email":"a1a416698dca08cf6c7b7feb5784300ff462ba1d@google.com","name":"Damien Miller"},"message":"package version metadata for external/\n\nThis will be used for automated notification of external vulnerability\nreports.\n\n(cherrypicked from commit 8dc37401ddfcb3c35b09eb02a06bd167a693bfff)\n\nChange-Id: Iaca4c74c644db5303382f1ab42c0aa154688a4a4","distinct":true,"url":"https://api.github.com/repos/NuclearCM/android_external_sqlite/commits/e6290514cfaa411ee82f4f0583ba34bf9eaa3c42"},{"sha":"bc0529073caa3a19ad5a68ac7917ff0018994208","author":{"email":"890a779b57f9f3eeefebb7cea4e2c1fc923cbd3c@gmail.com","name":"Moludos"},"message":"sqlite: upgrade to SQLite 3.9.2\n\nDownloaded from https://www.sqlite.org/2015/sqlite-amalgamation-3090200.zip\n\n  $ sha256sum sqlite-amalgamation-3090200.zip\n  567139c94375e3808a11f34d81f534d0c257e2c498cddbf4cac283d74b51fe9c  sqlite-amalgamation-3090200.zip\n\ndist/orig contains the stock sqlite3 code, as packaged in the ZIP file above.\n\ndist contains a copy of dist/orig, but with the Android.patch file applied.\nPlease see Android.patch for a list of differences between stock and\nAndroid.\n\nOne Android specific patch failed to apply cleanly. However, this patch was\na whitespace only patch, so it has been dropped from Android.patch. All\nother android specific patches applied cleanly.\n\nChanges since 3.8.10.2 (from https://www.sqlite.org/changes.html):\n\n  2015-11-03 (3.9.2)\n\n  * Fix the schema parser so that it interprets certain (obscure and ill-formed)\n  CREATE TABLE statements the same as legacy. Fix for ticket ac661962a2aeab3c331\n  * Fix a query planner problem that could result in an incorrect answer due to\n  the use of automatic indexing in subqueries in the FROM clause of a correlated\n\n  2015-10-16 (3.9.1)\n\n  * Fix the json1 extension so that it does not recognize ASCII form-feed as a\n  whitespace character, in order to comply with RFC-7159. Fix for ticket\n  57eec374ae1d0a1d\n  * Add a few #ifdef and build script changes to address compilation issues that\n  appeared after the 3.9.0 release.\n\n  2015-10-14 (3.9.0)\n\n  Policy Changes:\n\n  The version numbering conventions for SQLite are revised to use the emerging\n  standard of semantic versioning.\n\n  New Features And Enhancements:\n\n  * Added the json1 extension module in the source tree, and in the amalgamation.\n  Enable support using the SQLITE_ENABLE_JSON1 compile-time option.\n  * Added Full Text Search version 5 (FTS5) to the amalgamation, enabled using\n  SQLITE_ENABLE_FTS5. FTS5 will be considered \"experimental\" (subject to incompatible\n  changes) for at least one more release cycle.\n  * The CREATE VIEW statement now accepts an optional list of column names following\n  the view name.\n  * Added support for indexes on expressions.\n  * Added support for table-valued functions in the FROM clause of a SELECT statement.\n  * Added support for eponymous virtual tables.\n  * A VIEW may now reference undefined tables and functions when initially created.\n  Missing tables and functions are reported when the VIEW is used in a query.\n  * Added the sqlite3_value_subtype() and sqlite3_result_subtype() interfaced\n  (used by the json1 extension).\n  * The query planner is now able to use partial indexes that contain AND-connected\n  terms in the WHERE clause.\n  * The sqlite3_analyzer.exe utility is updated to report the depth of each btree and\n  to show the average fanout for indexes and WITHOUT ROWID tables.\n  * Enhanced the dbstat virtual table so that it can be used as a table-valued function\n  where the argument is the schema to be analyzed.\n\n  Other changes:\n\n  * The sqlite3_memory_alarm() interface, which has been deprecated and undocumented\n  for 8 years, is changed into a no-op.\n\n  Important fixes:\n\n  * Fixed a critical bug in the SQLite Encryption Extension that could cause the database\n  to become unreadable and unrecoverable if a VACUUM command changed the size of the\n  encryption nonce.\n  * Added a memory barrier in the implementation of sqlite3_initialize() to help ensure\n  that it is thread-safe.\n  * Fix the OR optimization so that it always ignores subplans that do not use an index.\n  * Do not apply the WHERE-clause pushdown optimization on terms that originate in the\n  ON or USING clause of a LEFT JOIN. Fix for ticket c2a19d81652f40568c.\n\n  2015-07-29 (3.8.11.1)\n\n  * Restore an undocumented side-effect of PRAGMA cache_size: force the database\n  schema to be parsed if the database has not been previously accessed.\n  * Fix a long-standing problem in sqlite3_changes() for WITHOUT ROWID tables that was\n  reported a few hours after the 3.8.11 release.\n\n  2015-07-27 (3.8.11)\n\n  * Added the experimental RBU extension. Note that this extension is experimental\n  and subject to change in incompatible ways.\n  * Added the experimental FTS5 extension. Note that this extension is experimental\n  and subject to change in incompatible ways.\n  * Added the sqlite3_value_dup() and sqlite3_value_free() interfaces.\n  * Enhance the spellfix1 extension to support ON CONFLICT clauses.\n  * The IS operator is now able to drive indexes.\n  * Enhance the query planner to permit automatic indexing on FROM-clause subqueries\n  that are implemented by co-routine.\n  * Disallow the use of \"rowid\" in common table expressions.\n  * Added the PRAGMA cell_size_check command for better and earlier detection of database\n  file corruption.\n  * Added the matchinfo 'b' flag to the matchinfo() function in FTS3.\n  * Improved fuzz-testing of database files, with fixes for problems found.\n  * Add the fuzzcheck test program and automatically run this program using both SQL\n  and database test cases on \"make test\".\n  * Added the SQLITE_MUTEX_STATIC_VFS1 static mutex and use it in the Windows VFS.\n  * The sqlite3_profile() callback is invoked (by sqlite3_reset() or sqlite3_finalize())\n  for statements that did not run to completion.\n  * Enhance the page cache so that it can preallocate a block of memory to use for the\n  initial set page cache lines. Set the default preallocation to 100 pages. Yields about\n  a 5% performance increase on common workloads.\n  * Miscellaneous micro-optimizations result in 22.3% more work for the same number of\n  CPU cycles relative to the previous release. SQLite now runs twice as fast as version\n  3.8.0 and three times as fast as version 3.3.9. (Measured using cachegrind on the\n  speedtest1.c workload on Ubuntu 14.04 x64 with gcc 4.8.2 and -Os. Your performance\n  may vary.)\n  * Added the sqlite3_result_zeroblob64() and sqlite3_bind_zeroblob64() interfaces.\n\n  Important bug fixes:\n\n  * Fix CREATE TABLE AS so that columns of type TEXT never end up holding an INT\n  value. Ticket f2ad7de056ab1dc9200\n  * Fix CREATE TABLE AS so that it does not leave NULL entries in the sqlite_master\n  table if the SELECT statement on the right-hand side aborts with an error.\n  Ticket 873cae2b6e25b\n  * Fix the skip-scan optimization so that it works correctly when the OR optimization\n  is used on WITHOUT ROWID tables. Ticket 8fd39115d8f46\n  * Fix the sqlite3_memory_used() and sqlite3_memory_highwater() interfaces so that\n  they actually do provide a 64-bit answer.\n\nChange-Id: Ic59c75950fe54b2ae3a2dabe5fe22f3fb4225e83","distinct":true,"url":"https://api.github.com/repos/NuclearCM/android_external_sqlite/commits/bc0529073caa3a19ad5a68ac7917ff0018994208"},{"sha":"9f0e55a2edff5041a6796d1563b8a2099fd91e38","author":{"email":"a6467e43e345e479bdff1ec4fa8b90b002319695@gmail.com","name":"Dave Kessler"},"message":"Reduce sync safety levels from 3 to 1\n\nbenchmarks were done with RL Benchmark: SQLITE 1.3\n\nBenchmark without this patch:\n\nOverall: 21,39 seconds\n\nBenchmark with this patch:\n\nOverall: 12,13 seconds\n\n* This patch improves the sqlite speed by ~44%\n\nThanks to dorimanx for helping me out with this patch.\n\nChange-Id: Ibb71dc369e2a8ece9c1fc31b51badc3eafe69b33\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>","distinct":true,"url":"https://api.github.com/repos/NuclearCM/android_external_sqlite/commits/9f0e55a2edff5041a6796d1563b8a2099fd91e38"}]}