Closed Bug 2053824 Opened 2 months ago Closed 1 month ago

Migrate History.fetchMany chunked IN-clause queries to array binding

Categories

(Toolkit :: Places, task, P3)

task

Tracking

()

RESOLVED FIXED
155 Branch
Tracking Status
firefox155 --- fixed

People

(Reporter: cachan, Assigned: cachan)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sng])

Attachments

(1 file)

As part of the leftover-inventory audit in bug 2042102 (blocking meta bug 2042084 "Replace IN clauses with array bindings in Places"), History.fetchMany's inner implementation (toolkit/components/places/History.sys.mjs, fetchMany) still chunks its guidOrURLs input via PlacesUtils.chunkArray(guidOrURLs, db.variableLimit) and builds url_hash IN(hash(?),...), url IN(?,...), and guid IN(?,...) clauses via PlacesUtils.sqlBindPlaceholders before running a SELECT against moz_places.

This should be migrated to use Sqlite.sys.mjs array binding (added in bug 1924124) instead of manual chunking + IN(?,?,?) placeholder lists, following the pattern used in the already-landed sibling bugs (2042085, 2042088-2042097).

Priority: -- → P3
Whiteboard: [sng]
Assignee: nobody → cachan
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
QA Whiteboard: [qa-triage-done-c156/b155]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: