In the done dashboard I have about 1400 items, though when backing up my chandler database it claims that it's trying to export about 12,000 items.
The count of records (presented during routine export to backup.chex) in the underlying database is naturally greater than the number of items presented in the table during normal use of Chandler Desktop. … causing some operations (like backup) to be rather slow. Around once a week, if you're lucky (most people are): * Chandler Desktop will take longer than usual to start * leading to improved performance for the week ahead. If you're unlucky (maybe I'm alone), the weekly routine will be bugged by <https://bugzilla.osafoundation.org/show_bug.cgi?id=12693>. Does anyone have any suggestions for how to handle archiving historical data? For the future: <https://bugzilla.osafoundation.org/show_bug.cgi?id=12233> refers to discussion of options that may be of interest to you. For now: if you sync Chandler Desktop with Chandler Hub, then you may use a CalDAV client such as Apple iCal to archive (copy then delete) selected items from the Hub. Hint: when you access Chandler Hub through the web, it will show fewer items than are actually on the Hub. This is by design, but not well explained. Regards Graham -- View this message in context: http://n2.nabble.com/Large-chandler-database-tp2435014p2530551.html Sent from the Chandler users mailing list archive at Nabble.com. _______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
