Closed
Bug 961093
Opened 11 years ago
Closed 11 years ago
Improve SQLiteBridge performance
Categories
(Firefox for Android Graveyard :: Data Providers, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Margaret, Unassigned)
References
Details
(Whiteboard: shovel-ready)
Instead of passing raw data over the bridge and creating a MatrixCursor, we've been discussing creating some sort of native cursor implementation.
I'll let wesj take the technical lead on this bug, since he's most familiar with the state of things here.
Flags: needinfo?(wjohnston)
|
||
Comment 1•11 years ago
|
||
Android's native CursorWindow implementation is here:
http://androidxref.com/4.2.2_r1/xref/frameworks/base/include/androidfw/CursorWindow.h
Might be able to reuse a bit (although there's definately an impedence match between this and our current implementation).
Flags: needinfo?(wjohnston)
|
Reporter | |
Updated•11 years ago
|
Whiteboard: shovel-ready
|
|
Reporter | |
Updated•11 years ago
|
Priority: -- → P1
|
|
Reporter | |
Updated•11 years ago
|
Priority: P1 → P2
|
|
Reporter | |
Comment 2•11 years ago
|
||
This is actually turning out to not be so bad in practice. We can make this bug a priority if this ever becomes a bigger problem.
Priority: P2 → --
|
|
Reporter | |
Comment 3•11 years ago
|
||
We can file new bugs as we find specific problems.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
|
||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•