Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

same_schema --exclude behaves differently from all other actions #31

Open
phinjensen opened this issue Jun 19, 2013 · 0 comments
Open

Comments

@phinjensen
Copy link

ID: 75
Version: unspecified
Date: 2011-04-19 08:27 EDT
Author: Peter Eisentraut (peter_e@gmx.net)


Although the documentation is technically correct on this, it would be really
helpful to make it crystal clear that in the same_schema action the --exclude
options works on a completely different logic than in most other actions that
follow the scheme explained in the section "BASIC FILTERING".

I would change this paragraph

"You may exclude all objects of a certain name by using the "exclude" option.
It takes a Perl regular expression as its argument."

to

"You may exclude all objects of a certain name by using the "exclude" option.
It takes a Perl regular expression as its argument. The option can be repeated
to specify multiple patterns to exclude. (Note that the --exclude option for
this action does not follow the logic explained in the "BASIC FILTERING"
section.)"

The alternative would be to eliminate this distinction, but that might break
too many things for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant