[Lxr-dev] [ lxr-Feature Requests-3578866 ] Add date of last indexation

[SourceForge.net <no...@so...>]

Feature Requests item #3578866, was opened at 2012-10-21 02:16
Message generated for change (Comment added) made by ajlittoz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3578866&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Lukasz M (myny)
Assigned to: Andre-Littoz (ajlittoz)
Summary: Add date of last indexation

Initial Comment:
I run lxr indexation on regular basis. I would like to know if run was successful or not. Would it be possible to add date/time of last successful run somewhere on the page? Or have a separate page with history of successful/failed runs.

----------------------------------------------------------------------

>Comment By: Andre-Littoz (ajlittoz)
Date: 2012-11-07 06:13

Message:
What is the definition of "successful run"? or a "failed run"?

Presently, there is nearly no status information returned. There are too
many independent software layers with their own ways of reporting what they
consider an error.

For example, DB errors are "displayed" with an error message, but when it
returns back to Perl, then to LXR, this information is lost!

Globally, genxref is a dispatcher. If spawning an operation is OK, it
considers it a "success", no matter how the dispatched task behaves.

I have already implemented part of the "indexing time" column. It can give
2 pieces of information:
1- whether the file really went through a parser (if not, column is blank;
e.g. .txt files)
2- whether the DB state is up-to-date with file state (if indexing time is
BEFORE file revision time, then cross-references are not valid).

For item 2, I'm having some trouble with svn. In the end, I could give a
background color (light red) in directory listing for files which
cross-references are not valid. I could also add a warning at the top of
file content. And maybe, why not, have a background in identifier search
for references in files which cross-refs are invalid.

Would that be of any help for your concern?

----------------------------------------------------------------------

Comment By: Lukasz M (myny)
Date: 2012-11-07 03:27

Message:
Well, it's not really what I was thinking about. I was hoping to have last
date of successful run of genxref (for each tree and version). Or last
couple of runs - successful and failed ones. But its ok to not have this
feature. :) Maybe later.

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2012-11-05 06:57

Message:
Oh! I missed that point. Following your remark, I can add a field in
lxr_status (which is associated with each base version of a file). With
this implementation there would be a date with each file. There is no DB
table associated with a "version" (because "versions" are rather virtual
with some storage, such as CVS or Git).

If date is in lxr_status, its retrieval is for free. The drawback is I
can't provide it in identifier search (at least until I get a result).

Also, when you index your tree incrementally, date for "file already
indexed" does not change; date is updated only for changed files.

Proposal:
- directory listing: a new column with date of last indexation
- file display: a line with date of last indexation

What do you think?

----------------------------------------------------------------------

Comment By: Lukasz M (myny)
Date: 2012-11-05 02:53

Message:
I think it would be ok. Would there be a date per each version for given
tree?

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2012-11-02 05:47

Message:
Would it be right if the date of last indexation appears in the showconfig
page?
This way, the DB would be queried for this date only when that page is
requested. Otherwise, if the date is printed in header/footer area, DB is
queried for every page displayed. Note this is relatively unimportant
because of the numerous other DB accesses. This could also be displayed in
ident page where it is important to be aware of result relevancy.

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2012-11-01 01:22

Message:
Transferred from "support request" to "feature request"

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2012-10-21 08:33

Message:
The structure of the database is not compatible with an indexing history
(in my opinion): there is provision for only one state of the references.
Once genxref has begun its work, it should go to the end (unless something
is wrong with the access rights). The only case of inconsistent DB is that
latter error.

I will experiment with a new table to contain a time stamp and put it
somewhere in the header or footer.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=3578866&group_id=27350