234
edits
User:Sspitzer/GlobalFrecency: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 196: | Line 196: | ||
31) | 31) | ||
email drhipp about indexing and SQLite LIKE contain searches or find the doc about how that doesn't work (marco's comments, too) | |||
32) | |||
we use last <n> visits. if all <n> are embed, but earlier visits were not, when we calculate frecnecy, we could end up with zero, even though the n+1 visit is typed. is this a spin off bug (I think so). we could make sure that if a place as at least 1 non 0,4 visit, we give it a non-zero frecency, or some other idea to prevent this bug. | |||
32) add comment about why we can't trust visit_count (from older versions) (we counted embed!) | |||
'''todo''' | '''todo''' | ||
x) after fx 2 / fx 3b2 migration, force a few idles? do a massive frecency recalc? how long does each take? do a few on a timer, not on idle to improve the first impression | x) after fx 2 / fx 3b2 migration, force a few idles? do a massive frecency recalc? how long does each take? do a few on a timer, not on idle to improve the first impression | ||
| Line 216: | Line 222: | ||
// as livemarks feeds yet. | // as livemarks feeds yet. | ||
less of a deal as | less of a deal as typical bookmarks are much fewer than history? not sure. | ||
note, calling FixInvalidFrecenciesForExcludedPlaces() from from the places import / export code means adding it to the nsINavHistoryService interface | note, calling FixInvalidFrecenciesForExcludedPlaces() from from the places import / export code means adding it to the nsINavHistoryService interface | ||