default schema / schema translation map as an execution argument
Issue #2685
resolved
this comes up a lot, the need to swap in a schema name for all tables. this is an easy add as an execution option, most of a patch is attached, needs tests.
Comments (10)
-
reporter -
reporter - changed milestone to 0.9.0
-
reporter - changed milestone to 0.9.xx
-
reporter this patch works for rendering but isn't taken into account by the inspector. needs that also.
-
reporter - changed milestone to 1.0.xx
-
reporter - changed milestone to 1.1
-
reporter we might want to look into providing a "swap" feature, e.g. if an app has tables in "(default)", "schema_a", "schema_b", a lookup table can be sent in such that any of these three can be exchanged for another.
-
reporter - changed title to default schema / schema translation map as an execution argument
-
reporter -
reporter - changed status to resolved
- Multi-tenancy schema translation for :class:
.Table
objects is added. This supports the use case of an application that uses the same set of :class:.Table
objects in many schemas, such as schema-per-user. A new execution option :paramref:.Connection.execution_options.schema_translate_map
is added. fixes#2685 - latest tox doesn't like the {posargs} in the profile rerunner
→ <<cset 89facbed8855>>
- Log in to comment
the usage pattern would be like:
to generate the SQL plain looks like: