summaryrefslogtreecommitdiff
path: root/db/sqlite3
Commit message (Collapse)AuthorAge
* No issue - Update SQLite lib to 3.42.0Moonchild2023-06-19
|
* Issue #1829 - Revert “Issue #1751 - Remove Mac code behind ↵Brian Smith2022-04-26
| | | | | | MOZ_WIDGET_TOOLKIT == 'cocoa’” This reverts commit 1fe9c19305dadf2d5bcaa0e589fcd250389dfa8a.
* [db] Update SQLite to 3.36.0Moonchild2021-08-13
|
* Issue #1751 - Remove Mac code behind MOZ_WIDGET_TOOLKIT == 'cocoa'Moonchild2021-06-21
|
* Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23
|
* Issue #457 - Silence SQLite compiler warningMoonchild2020-08-18
| | | | | | | | | | | | | Our use of SQLite explicitly avoids using MSVC's _msize which the lib would notrmally use. This was set up this way in BZ bug 719579 for legitimate reasons (because _msize would end up using the system symbol, which would crash trying to get the size information from jemalloc allocations). Since we build the SQLite lib separately there is no easy way to avoid this warning as it's not directly linked against mozglue.dll which has the jemalloc functions it wants for _msize when not using the system allocator. It is implicitly assuming the function is an extern returning an int (with the call specifically casting to int) which is correct (well, correct _enough_, anyway) so the warning can safely be ignored for our specific use as it all lines up at link time.
* [db] Update SQLite lib to 3.33.0Moonchild2020-08-18
|
* Issue #1053 - Remove android support from dbMatt A. Tobin2020-02-25
|
* Issue #1457 - Unfold sqlite3 from nssMatt A. Tobin2020-02-20
|
* Issue #1254 - Update SQLite to 3.30.1wolfbeast2019-11-08
|
* Update SQLite to 3.29.0wolfbeast2019-07-28
|
* Update SQLite to 3.27.2wolfbeast2019-03-30
|
* Update SQLite lib to 3.26.0wolfbeast2018-12-18
|
* Update SQLite lib to 3.21.0.wolfbeast2018-03-29
|
* Update SQLite to 3.19.3.wolfbeast2018-02-04
|
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02