Hi David, Have you run Debug - Repository - Compact ? That needs to be run periodically to clean out and compact the repository.
Archiving old data is also a problem for me - since the done tasks are also a record of what was done, I need to preserve them, rather than just deleting old collections and at the moment there does not seem to be any way of doing this. I suspect that this is a reflection on the fact that no-one has been using Chandler for very long; no doubt the issue will come to the fore as time passes. Fritz 2009/7/27 David K. Kim <[email protected]> > Hello All, > > My Chandler repository was generated by importing .ics items originally > created mostly in Entourage. > > It is quite slow and seems to crash more often than I believe is true of > most (e.g. my wife’s, who has a smaller repository). I suspect there may be > some hidden logic bombs also with items not originally created in Chandler. > > > Given the limited resources for the project, I am not expecting the general > robustness or speed of the platform to improve quickly. However, I do like > the approach and would like to keep using it. Thus, I am searching for ways > to optimize. > > (1) What is the best way to “cull” old items from the repository? I have > sorted by date and manually deleted, after a full export. Yet some data > seems to persist. Will one of the ctrl/option-startup options cull the > associated metadata? > > (2) In general, how do people archive old Chandler data? > > Thanks for any thoughts, > David > > _______________________________________________ > [email protected] mailing list > unsubscribe here: > http://lists.osafoundation.org/mailman/listinfo/chandler-users > Chandler wiki: http://chandlerproject.org/wikihome >
_______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
