Opened 7 years ago

Last modified 7 years ago

#592 new defect

simfactory --mdbkey syntax is horrible

Reported by: Roland Haas Owned by: Erik Schnetter
Priority: minor Milestone:
Component: SimFactory Version:
Keywords: Cc:


apparently simfactory requires me to do:

sim --mdbkey=optionlist my-very-own-option-list

to overwrite mdb entries from the command line (and --define --substitue --replace --append --mdbkey). I have to admit I would not have guessed that from the help text which states:

  -h, --help            show this help message and exit
  --define=DEFINE       set additional definition
  --mdbkey=MDBKEY       override an mdb key

I would like to suggest to either change the help text to


or to support something like


with or without quotation marks instead maybe.

Is there a full documented list of valid mdb entries somewhere?

Attachments (0)

Change History (2)

comment:1 Changed 7 years ago by Ian Hinder

There is no such documentation at the moment. There is a file called simfactory/etc/syntax/mdb-syntax.ini which contains the information which is output with --help for the MDB entries. I think this is the place that these things should be documented, at least minimally. The command line options are documented in simfactory/etc/options, but this is a little confused at the moment and should be tidied up. The SimFactory user guide aims to parse these files and extract the documentation. This has been done for the command-line options but not for the MDB entries yet. See

comment:2 Changed 7 years ago by Roland Haas

Component: OtherSimFactory
Owner: set to Erik Schnetter

re-classify ticket

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain Erik Schnetter.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from Erik Schnetter to the specified user.
Next status will be 'confirmed'.
The owner will be changed from Erik Schnetter to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.