Attribute providers for the global database (gloda) may potentially create database rows as a side-effect of the indexing process. Gloda needs to provide a way of ensuring that these rows are not leaked. This mechanism needs to work both when the attribute provider is available and when it has gone missing (because it is part of a disabled/uninstalled extension, etc.) This bug is being created to track this need. Gloda is not yet in the trunk, and none of the proposed or implemented functionality for core is capable of leaking rows.
marking blocking rc1 per Andrew
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Summary: global database needs to have a means of ensuring attribute-owned rows are not leaked/orphaned → gloda needs to have a means of ensuring attribute-owned rows are not leaked/orphaned
assigning to asuth for triage
Assignee: nobody → bugmail
Removing blocking. We are nowhere near this being a problem or having an extension story where this could begin to be a problem.
Whiteboard: [no l10n impact] → [no l10n impact][gloda longterm]
Target Milestone: Thunderbird 3.0rc1 → Future
You need to log in before you can comment on or make changes to this bug.