Open
Bug 1336943
Opened 7 years ago
Updated 1 year ago
Evaluate using SQLITE_LIMIT_SQL_LENGTH
Categories
(Toolkit :: Storage, defect, P3)
Toolkit
Storage
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox54 | --- | affected |
People
(Reporter: mak, Unassigned)
References
(Depends on 1 open bug)
Details
Long queries in general may cause problems, and almost always there's a shorter and better way to handle the problem. Some sqlite APIs also have to do recursive work that may be really expensive on large queries. We should probably use sqlite3_limit(db, SQLITE_LIMIT_SQL_LENGTH, 250000) or a smaller value. But first we need to support binding arrays for IN clauses, so we can remove IN usage
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•7 years ago
|
||
note it would be nice to have telemetry about queries length, before doing this.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•