Closed Bug 1564889 (SQLite3.29.0) Opened 8 months ago Closed 8 months ago

Upgrade to SQLite 3.29.0

Categories

(Toolkit :: Storage, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: RyanVM, Assigned: RyanVM)

References

(Blocks 1 open bug, )

Details

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #1544443 +++

It's not actually out yet, but we found an issue with the latest snapshot build and wanted to be able to set deps for it.

Depends on: 1564894

And there it is!

2019-07-10 - Release 3.29.0

Version 3.29.0 is a regularly scheduled maintenance release of SQLite containing miscellaneous performance and feature enhancements. See the change log for details.

Beginning with this release, the double-quoted string literal misfeature is deprecated. The misfeature is still enabled by default, for legacy compatibility, however developers are encouraged to disable it at compile-time using the -DSQLITE_DQS=0 option, or at run-time using the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to the sqlite3_db_config() interface. This is especially true for double-quoted string literals in CREATE TABLE and CREATE INDEX statements, as those elements can cause unexpected problems following an ALTER TABLE. See ticket 9b78184be266fd70 for an example.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #1)

Beginning with this release, the double-quoted string literal misfeature is deprecated. The misfeature is still enabled by default, for legacy compatibility, however developers are encouraged to disable it at compile-time using the -DSQLITE_DQS=0 option, or at run-time using the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to the sqlite3_db_config() interface. This is especially true for double-quoted string literals in CREATE TABLE and CREATE INDEX statements, as those elements can cause unexpected problems following an ALTER TABLE. See ticket 9b78184be266fd70 for an example.

Is this something we care about?

Try push without that change:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=9e907409cfa13388ef529c13d73498057a4d40a8

Alias: SQLIte3.29.0 → SQLite3.29.0
Flags: needinfo?(mak77)

it is recommended, so we should at least file a followup to enable it.

Flags: needinfo?(mak77)

I did a Try push with SQLITE_DQS set to 0 and got a lot of orange. Looks like we'll indeed want to move that to a follow-up.
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=0e0c565c849bd9ac831794d51cf7a10858ddcc7f

I am going to remove the aarch64 byte order setting from moz.build, however, since that was fixed upstream in the 3.25 release.

Blocks: 1566144
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Blocks: SQLite3.30.1
You need to log in before you can comment on or make changes to this bug.