Bug #229: widget should use the content provider instead of looking into app's database directly - Widgets - Squall Line Software's Closed Source Projects

Actions

Copy link

Bug #229

closed

widget should use the content provider instead of looking into app's database directly

Added by Tony Ciavarella almost 12 years ago. Updated almost 12 years ago.

Status:

Closed

Priority:

High

Assignee:

Tony Ciavarella

Target version:

2.2.2

Start date:

05/12/2012

Due date:

% Done:

100%

Estimated time:

Description

It is dangerous for the widget to look directly into the app's sleep history database because when the schema is upgraded on one but not the other, the damn database version gets downgraded and upgraded repeatedly. That really freaking sucks and makes a terrible mess of things.

Using the content provider avoids all the evils.