Closed
Bug 18346
Opened 25 years ago
Closed 24 years ago
Need to keep summary of summary files file from getting stale
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
M18
People
(Reporter: Bienvenu, Assigned: Bienvenu)
References
Details
(Whiteboard: Fix in hand)
We need to keep the summary of summary files from getting stale, e.g., when we crash before updating it. In 4.x, this was done by deleting the file after opening it and recreating it anew each time we shut down. That would work for 5.0, but it would be much nicer to stick a time stamp in each folder, or something so we could have a partially valid summary and not load all databases at startup after every crash.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Assignee | ||
Comment 1•25 years ago
|
||
accepting, m14
Comment 2•25 years ago
|
||
Wouldn't hold b1 for this. David, what do you think?
Target Milestone: M14 → M15
Assignee | ||
Comment 3•25 years ago
|
||
I guess not, but it's very confusing for users. I guess we'd better just not crash :-(
Comment 6•24 years ago
|
||
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Putting on [nsbeta2-] radar. Not critical to beta2. Spoke with phil.
Whiteboard: [nsbeta2-]
Assignee | ||
Updated•24 years ago
|
Comment 10•24 years ago
|
||
recommend nsbeta3+
Assignee | ||
Updated•24 years ago
|
Whiteboard: Fix in hand
Assignee | ||
Comment 11•24 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 12•23 years ago
|
||
david, safe to mark this verified? I think summary files are working fine now and do get regenerated when I start mail after a crash.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•