summaryrefslogtreecommitdiffstats
path: root/third_party/sqlite/src/test/vacuum.test
Commit message (Collapse)AuthorAgeFilesLines
* Import SQLite 3.8.7.4.Scott Hess2015-02-101-7/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ran through the import script in third_party/sqlite/README.Chromium, including the SQLite test suite. There are a few pager errors which are because of a change required for WebDatabase support (documented in README). SQLite changes are at http://www.sqlite.org/changes.html , Chromium previously used 3.7.6.3. All patches were applied and the results reviewed to make sure backported patches were safe to remove, and retained patches were still covering what was necessary. Keep fts4 disabled, and also the new fts3 virtual table and unicode61 tokenizer. Once enabled, these are very hard to disable, and there doesn't seem to be any pressure to enable them. Other SQLITE_* flags were reviewed for applicability, none looked essential. Fixes to Chromium: - In recovery.cc, pk_column now follows the documentation. - Short garbage files now see SQLITE_NOTADB rather than SQLITE_IOERR_SHORT_READ. - Adjust to allow clients to use ScopedErrorIgnore without adding dependencies. - More-specific SQLITE_CONSTRAINT_* errors aren't necessary. - Force recovery test to scan table rather than index. BUG=340757 TEST=*EVERYTHING* continues to work. R=michaeln@chromium.org Review URL: https://codereview.chromium.org/901033002 Cr-Commit-Position: refs/heads/master@{#315646}
* Import SQLite 3.7.6.3.shess@chromium.org2011-05-251-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ran through the import script in third_party/sqlite/README.Chromium, including the SQLite test suite. A few minor errors under oserror-1.1.[123], I suspect my Linux reference machine is becoming outdated. SQLite changes are going to be hard/impossible to review. It's a year and a half of changes, might as well be a new package. Removed patches which are no longer necessary: icu-regepx.patch is already present safe-tolower.patch is already present attach-integer.patch no longer relevant For attach-integer.patch, the code has been refactored. The failure in http://crbug.com/38745 no longer occurs (ATTACH 12345 as db; attaches the SQLite database "12345" rather than crashing). Tweak test.patch for modern era. Adjusted webdb.patch for new flag. Clean up fts3.patch. fts3 has been substantially refactored, so much of the patch no longer applies. Reviewed fts3_write.c and many of the patches are now handled appropriately. I found one issue in fts3.c, and I'm still reviewing it. This will be ongoing. Disabled WAL (Write Ahead Log) and fts4 support for now as unknown unknowns. BUG=71731 TEST=*EVERYTHING* continues to work. Review URL: http://codereview.chromium.org/6990047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86616 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 68506 - Update sqlite to 3.7.3.jhawkins@chromium.org2010-12-071-13/+0
| | | | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5626002 TBR=jhawkins@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68531 0039d316-1c4b-4281-b951-d872f2087c98
* Update sqlite to 3.7.3.jhawkins@chromium.org2010-12-071-0/+13
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/5626002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68506 0039d316-1c4b-4281-b951-d872f2087c98
* Move bundled copy of sqlite one level deeper to better separate itphajdan.jr@chromium.org2010-08-181-0/+351
from our patches, READMEs, etc. Also, add a shim header so we can use it for building with system sqlite. TEST=compile BUG=22208 Review URL: http://codereview.chromium.org/3108030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56619 0039d316-1c4b-4281-b951-d872f2087c98