summaryrefslogtreecommitdiff
path: root/platform/default/sqlite3.hpp
Commit message (Collapse)AuthorAgeFilesLines
* [build] rework platform/default directory and add -files.txt for vendored libsKonstantin Käfer2018-12-141-181/+0
|
* [android] explicitly set temp directory for SQLite3Konstantin Käfer2018-09-261-0/+2
|
* [core] recreate offline database when it is deleted out from under our feetKonstantin Käfer2018-08-141-12/+13
|
* [core] consolidate database opening workflowKonstantin Käfer2018-06-121-3/+2
| | | | | | | | Before this change, we've tried to open the database in read/write, but not create mode. In situations where the database didn't exist yet, this logged an error to the console, and we proceeded to opening it again in read/write/create mode, which actually created the file. The reason we did this is so that we could detect really old caching databases from January 2016 in case a developer upgraded from an older SDK (iOS v3.1 and earlier, Android v3.2 and earlier) that didn't have https://github.com/mapbox/mapbox-gl-native/pull/3715 yet. However, these error messages, while innocent, look scary in the console and some users suspect that it's a bug. This change opens the file directly in read/write/create mode, omitting the first failed attempt. To handle old cache databases, we're now deleting the `http_cache` table, which was the only table in those old databases, and create the new schema, rather than deleting the entire file and recreating the Database object. In most scenarios, this will lead to one fewer opening attempt, while the database migration will continue to work for the few users who upgrade all the way from a January 2016 SDK. Additionally, this fixes a mismatch between the Qt and non-Qt implementation: Qt doesn't support opening a file in read/write mode without the create flag. This means that we've seen a different control flow on Qt compared to the non-Qt implementation when opening a database.
* [core] remove unused flags from SQLite headerKonstantin Käfer2018-06-121-4/+0
|
* [core] support moving Database object during a TransactionKonstantin Käfer2018-06-121-1/+3
|
* Avoid exceptions for flow control during database creationJohn Firebaugh2018-05-091-1/+5
| | | | Unfortuntely, it's difficult to avoid all exceptions, because sqlite3_open_v2 does not reliably return SQLITE_NOTADB if the file is not a database. However, this should avoid cases where developers misinterpret the SQLITE_CANTOPEN exception as a crash, which is the common case.
* [core, qt] move self-resetting Statement/Query object to shared headerKonstantin Käfer2018-03-021-12/+38
|
* [core] refactor SQLite error/status codesKonstantin Käfer2018-03-021-9/+42
|
* [core] Remove unused bool() functionsBruno de Oliveira Abinader2017-04-141-4/+0
|
* [core] Replace sqlite3.h dependency in offline databaseBruno de Oliveira Abinader2017-01-231-1/+7
|
* [core] Move sqlite::Statement::check to pimplBruno de Oliveira Abinader2017-01-231-2/+0
|
* [core] Move lastInsertRowId/changes to sqlite::StatementBruno de Oliveira Abinader2017-01-231-3/+3
|
* [core] Private implementation for SQLite interfaceBruno de Oliveira Abinader2017-01-231-7/+8
|
* [core] Move SQLite logging setup to before database initializationJason Wray2016-09-091-1/+1
| | | | | | - Ensure that sqlite3_config() is always called before db init. - Should only be called once, now. - Move sqliteVersionCheck into mapbox::sqlite namespace.
* [core] Implement SQLite error logging (#6291)Jason Wray2016-09-081-0/+1
|
* [core] Avoid redundant 'inline' usageBruno de Oliveira Abinader2016-06-181-2/+2
|
* [core] Fix race condition that could lead to a UNIQUE constraint failure (#4677)John Firebaugh2016-04-111-0/+24
|
* [core] Implement an eviction policy for OfflineDatabaseJohn Firebaugh2016-02-101-0/+1
| | | | | | | | | | | | | When inserting an cached resource, or removing a region, remove least-recently used resources and tiles, not used by offline regions, until the used database size, as calculated by multiplying the number of in-use pages by the page size, is less than the maximum cache size minus 5 times the page size. In addition, OfflineDatabase may be configured to ignore cache puts of individual resources larger than a certain size. This policy is similar but not identical to the former SQLiteCache policy: * It accounts for offline, by exempting resources required by offline regions from eviction. * It must delete from two tables (resources and tiles), rather than one. Currently the strategy is naive: evict 50 rows at a time from each table. * It makes maximumCacheSize and maximumCacheEntrySize completely independent. The SQLiteCache implementation evicted when `usedSize > maximumCacheSize - 2 * maximumCacheEntrySize`. This evicts when `usedSize > maximumCacheSize - 5 * pageSize`. * It uses a non-unlimited default value for maximumCacheSize: 50 MB. We should have always had a limit in place; "a cache without an eviction policy is a resource leak".
* [core] Reset SQLite statements after use in order to release locksJohn Firebaugh2016-02-101-0/+1
|
* [core] Disable SQLite busy timeouts so that multiple readers can access the ↵John Firebaugh2016-02-101-0/+2
| | | | same database
* [core] Explicit operator boolJohn Firebaugh2016-02-101-2/+2
|
* [core] Interface and implementation for offlineJohn Firebaugh2016-02-101-1/+12
|
* [core] Eliminate macros in sqlite3.cppJohn Firebaugh2016-01-191-0/+2
|
* [core] throw values, catch referencesKonstantin Käfer2015-12-031-0/+1
|
* make storage lib separate so we can build without storage libsKonstantin Käfer2015-02-041-0/+74
View Lorry Controller Status