[ditrack commit] r2407 - src/trunk/DITrack/DB

[Vlad Skvortsov]

Ivan Glushkov wrote:
>>  > But, I think we need to implement command to clear cache
>>  >
>>  > "dt cleanup" or "dt --clear-cache ls" or "dt --without-cache ls"
>>  >
>>  > because we can't predict all possible cases of cache clearing:
>>  > - delete one of comment manually
>>  > - delete one of issue manually
>>  > - etc
>>  >
>>  > Your opinion?
>>
>>
>> I think *for now* we can skip it. We can always recommend users to
>>  remove the cache file manually and if people get annoyed by doing this,
>>  we'll know that and implement a command. :-)
>>     
>
> I'd like to vote to the Oleg's proposition. Let's compare the
> following two methods of clearing cache:
> - 'rm issues/.ditrack/.cache'
>     do the user always remember where this cache-file is located? I
> suppose no. How should it recall it? 'grep cache -r *' (hoping that we
> mentioned it in some README file)
> - 'dt cleanup'
>     it's the usual interface with the user, so it'll always get help
> by 'dt --help'.
>   

I still stand by my opinion that there is no need to add this complexity 
right away. We do have a mechanism for automatic cache repopulation so 
for %99.99 cases of regular usage there should be no need to even think 
about the cache. When things get hosed, there is always an option of 
just removing the working copy and checking it out afresh.

So I think there is no need to consider adding new commands at least 
until we see user requests/complaints.

-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com