gen-index (maybe a bug)

[Dirk Schenkewitz]

Hi guys :-)

While migrating our databases from Gnats 3.113 to 3.999,
I wanted to get a text-index first. Then I discovered that
calling 'gen-index -e' refused to work, giving the usage
message and doing nothing else.
My dbconfig-file contained the following (without comments):
------------------------------------------------------------
index {
    path "index"
    fields {
        "Submitter-Id" "Responsible" "State" "Confidential" "Severity"
        "Priority" "Date-Required" "Keywords" "Arrival-Date"
        "Last-Modified" "Closed-Date" "Class" "Originator"
        "Synopsis" "Organization" "Version" "Operating-System"
    }
    binary-index true
}
------------------------------------------------------------

After some frustrating attempts, I changed the above into:
------------------------------------------------------------
index {
    path "index.txt" # "index"
    fields {
        "Submitter-Id" "Responsible" "State" "Confidential" "Severity"
        "Priority" "Date-Required" "Keywords" "Arrival-Date"
        "Last-Modified" "Closed-Date" "Class" "Originator"
        "Synopsis" "Organization" "Version" "Operating-System"
    }
    binary-index false # true
}
------------------------------------------------------------

and called 'gen-index' without any parameter - and it worked.


Is this behaviour normal ?
(I found no hint in the docs about it - I thought specifying '-e'
would override the "binary-index true".)

Nice work, btw. - It is a GREAT step forward from Gnats 3.113 :-)

greetings
        dirk
-- 
Dirk Schenkewitz 

InterFace AG                 fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16            fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching         
http://www.interface-ag.de   mailto:dirk.schenkewitz@interface-ag.de