Postgres schema support about agnostic HOT 5 CLOSED

I like your suggestion: the database name option should be called --database and --schema should mean the schema name. One question: should --schema take a list of schema names, like --schema foo,bar,public?

This will require some rewriting of docs and unit tests. Is this something you can send a pull request for? If not, I can get to it sometime in December.

from agnostic.

I can probably do a pull request, though I might not get to it immediately. I think taking multiple schema names would be useful, as would some kind of ability to run against all non-public schemas.

from agnostic.

Ok. Let me know if you do get started on it, so that we don't duplicate effort. If I get started first, I'll let you know.

from agnostic.

Hey @patrick-jones I've just pushed an implementation of what we discussed about renaming --schema to --database and adding a new --schema flag in its place. It supports Postgres search paths, including the special $user path, e.g. ``--schema '"$user",public'`. I did not implement the "run against all non-public schemas" feature.

I tested this carefully to verify that it works as I think it should, but I don't use schemas myself (I put everything in public), so I could use your feedback on whether this works as you expect it to.

from agnostic.

Sorry for ignoring you -- I'll try to look into this soon.

from agnostic.