Bug #227
Case insensitive file and directory names
| Status: | Closed | Start: | 08/07/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Indexer | |||
| Target version: | SupoSEWeFE 0.1.0 | |||
Description
Since the more recent version of SupoSE was released (0.60 I think), the file and directory names are now all lower case. I had developed a web front end for me to use to search the index, and I had used these fields to construct links to Trac and the source files.
Unfortunately since this change these links are now broken as the URL's are case sensitive and there is no way to reconstruct the case used for the file and path.
I understand the benefits for searching of having these values in lower case but is there some way the original values could be preserved?
I'm not sure whether this should be classed as a bug or a feature request.
History
Updated by Karl Heinz Marbaise 1015 days ago
Hi Stephen,
Since the more recent version of SupoSE was released (0.60 I think), the file and directory names are now all lower case. I had developed a web front end for me to use to search the index, and I had used these fields to construct links to Trac and the source files. Unfortunately since this change these links are now broken as the URL's are case sensitive and there is no way to reconstruct the case used for the file and path. I understand the benefits for searching of having these values in lower case but is there some way the original values could be preserved?
That's correct. There are two different sets of fieldnames (filename, path) which are lowercase but there is an other set of fieldnames (dfilename, dpath) which have stored the folder and filenames in their original case. So these fields have to be used...
That's exactly the problem i had....my minial Web-Front-End is working the same way...
I'm not sure whether this should be classed as a bug or a feature request.
That depends...may be i have had to put this kind of information into the changelog and better explanained that...
sorry...
EDIT: Updated the Release Notes for 0.6.0
BTW: May be you can contribute the web-Front-End (or at least) the ideas you're using...in relationship with Trac might be very interesting..
Kind regards
Karl Heinz Marbaise
Updated by Stephen McGarry 1015 days ago
Hi Karl,
Thanks for the quick response - I hadn't realised there were additional fieldnames so that is good news.
The web front end I created was pretty simple - I created an ASP.NET page, and used a build of Lucene.NET to enable me to construct a query against the index. Problems I encountered were generally matching the versions of the index with the ones you used for constructing it.
I haven't created a plugin for Trac, though that would be ideal. Instead I just added a button to the main Trac page which links to the search page.
Updated by Stephen McGarry 1015 days ago
- File SubversionSearch.zip added
- Status changed from New to Closed
I've attached my simple web front end. The zip file includes my build of Lucene.NET which I used to interface to the index created by SupoSE.
I'll close this issue now as your alternative field names work fine.
Thanks.
Updated by Karl Heinz Marbaise 1015 days ago
Hi Stephen,
I've attached my simple web front end. The zip file includes my build of Lucene.NET which I used to interface to the index created by SupoSE.
Cool...thanks....I couldn't test or use it cause I'm working on Linux and Mac OS....but others might be interessted in it....
I hope it's allowed that others use it ? (und GPL ? as SupoSE itself ?)
I'll close this issue now as your alternative field names work fine.
That's good to hear...
Thank you...
Kind regards
Karl Heinz Marbaise
Updated by Karl Heinz Marbaise 1015 days ago
- Target version set to SupoSEWeFE 0.1.0
Updated by Stephen McGarry 1015 days ago
I'm not sure it is ready for other people to use as it stands, but it is probably a reasonable place to start so I have no problem with that. I think the Lucene.NET library uses the Apache licence.