New dbconfig keyword multi-enumerated-in-file

New dbconfig keyword multi-enumerated-in-file

[Johannes Poehlmann]

Hi,

We wanted to have fields of type Multi-Enum where
the allowed values are stored in an extra file like 
it is done with the Enumerated-in-File type.

I made a little patch to make this possible.

The patch built and seemed to give reasonable results with query-pr.

How to test: 
	Take a dbconfig file and replace enumerated-in-file with 
	multi-enumerated-in-file for a field "FIELD". 
	Now query-pr with the options
	  --field-type=FIELD      --valid-values=FIELD
	you will see tye MultiEnum and the values from the file.

Todo:
      Documentation not updated.
      not tested in full integration
-- 
     ______   ___        
    /  ___/__/  /                 Caldera (Deutschland) GmbH          
   /  /_/ _  / /__        Naegelsbachstr. 49c, 91052 Erlangen, Germany 
  /_____/_/ /____/                  http://www.caldera.de       
 ==== /____/ =====   Dipl. Inf. Johannes Poehlmann, mail: jhp@caldera.de
Caldera OpenLinux    phone: ++49 9131 7192 335, fax: ++49 9131 7192 399

Re: New dbconfig keyword multi-enumerated-in-file

[Milan Zamazal]

>>>>> "JP" == Johannes Poehlmann <jhp@caldera.de> writes:

    JP> We wanted to have fields of type Multi-Enum where the allowed
    JP> values are stored in an extra file like it is done with the
    JP> Enumerated-in-File type.

Good idea.

    JP> I made a little patch to make this possible.

Thanks, it should appear in CVS soon.  I also added the `separator'
option.

    JP> Todo: Documentation not updated.

Updated.

    JP> not tested in full integration

Not tested by me at all (except compilation), please test.

Regards,

Milan Zamazal

-- 
  _/_\_/_  o     _\_/_\_  o     _/_\_/_  o     _\_/_\_  o    BEWARE!
-<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--   *Bugs* are
   / \ /   o      \ / \   o      / \ /   o      \ / \   o     approaching!