Closed
Bug 892447
Opened 12 years ago
Closed 12 years ago
[SMS] 'getMessages': Handle errors in cursor properly
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 893838
People
(Reporter: borjasalguero, Unassigned)
References
Details
We need to ensure the right management of errors during the 'getMessages' request to Gecko.
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Comment 1•12 years ago
|
||
Here we are going to address the following suggestion:
Gabriele Svelto [:gsvelto]:
> (In reply to Chuck Lee [:chucklee] from comment #38)
> > I noticed that, the deleting process are assuming every operation will
> > success.
> > If there's an |cursor.onerror| in the |getMessages()|, the DOMs are deleted,
> > but messages in DB are not.
> > Maybe we need a way to recovery these DOMs should this happens?
>
> I think the best way would be to invert the order in which we're doing
> operations, i.e. gather all messages from the threads we want to delete
> (using |cursor.onerror| to exclude the threads for which we hit errors),
> delete the messages and then remove the threads we're sure we have deleted
> from the DOM in one go.
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → fbsc
Reporter | ||
Updated•12 years ago
|
blocking-b2g: --- → koi?
Reporter | ||
Updated•12 years ago
|
Assignee: fbsc → nobody
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
blocking-b2g: koi? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•