On Wed, Jun 10, 2020 at 05:03:49AM +0200, Pavel Stehule wrote:
> st 10. 6. 2020 v 0:30 odesílatel Justin Pryzby <pryzby@telsasoft.com> napsal:
>
> > On Tue, Jun 09, 2020 at 11:46:24AM +0200, Pavel Stehule wrote:
> > > po 8. 6. 2020 v 23:30 odesílatel Justin Pryzby <pryzby@telsasoft.com> napsal:
> >
> > > I still wonder if a better syntax would use a unified --filter option, whose
> > > > argument would allow including/excluding any type of object:
> > > I tried to implement simple format "[+-][tndf] objectname"
>
> I had another idea about format - instead using +-, we can use case
> sensitive options same to pg_dump command line (with extending Df -
> because these options doesn't exists in short form)
>
> So format can looks like
>
> [tTnNDf] {objectname}
>
> What do you think about this? This format is simpler, and it can work. What
> do you think about it?
I prefer [-+][dtnf], which is similar to rsync --filter, and clear what it's
doing. I wouldn't put much weight on what the short options are.
I wonder if some people would want to be able to use *long* or short options:
-table foo
+schema baz
Or maybe:
exclude-table=foo
schema=bar
Some tools use "long options without leading dashes" as their configuration
file format. Examples: openvpn, mysql. So that could be a good option.
OTOH, there's only a few "keys", so I'm not sure how many people would want to
repeat them, if there's enough to bother putting them in the file rather than
the cmdline.
--
Justin
