The automatic usage information in the help for sdiff and sintersect is misleading/wrong. If the database is given after -l or -s, it is interpreted as another element in those sets, and the invocation fails due to a "missing" database argument.
The underlying problem is one of parsing a command that has more than one variable length list of argument values, but the current practical solution is to make it explicit in the help text that the order in the example command given is the way to go.
The automatic usage information in the help for
sdiff
andsintersect
is misleading/wrong. If the database is given after -l or -s, it is interpreted as another element in those sets, and the invocation fails due to a "missing" database argument.The underlying problem is one of parsing a command that has more than one variable length list of argument values, but the current practical solution is to make it explicit in the help text that the order in the example command given is the way to go.