summaryrefslogtreecommitdiff
path: root/docs/build/cookbook.rst
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2020-04-27 19:02:57 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2020-04-27 19:02:57 -0400
commit0d9a42bcd686b4afa9d2da90e09b76284b50942a (patch)
tree5a2a6fb9498e2536c87fcca9e73f201efb47d927 /docs/build/cookbook.rst
parent5b83948827b5543e388f5164af63929ca3af7312 (diff)
downloadalembic-0d9a42bcd686b4afa9d2da90e09b76284b50942a.tar.gz
Add link to Alembic Utils as an example of replaceable objects.
Change-Id: I9f8f423a363970814d2ca5fea2c0b2c35c34d19d References: #686
Diffstat (limited to 'docs/build/cookbook.rst')
-rw-r--r--docs/build/cookbook.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/build/cookbook.rst b/docs/build/cookbook.rst
index 83cabdb..324c580 100644
--- a/docs/build/cookbook.rst
+++ b/docs/build/cookbook.rst
@@ -270,6 +270,14 @@ what we might call a *replaceable* schema object. A replaceable object
is a schema object that needs to be created and dropped all at once.
Examples of such objects include views, stored procedures, and triggers.
+.. seealso::
+
+ The Replaceable Object concept has been integrated by the
+ `Alembic Utils <https://github.com/olirice/alembic_utils>`_ project,
+ which provides autogenerate and migration
+ support for PostgreSQL functions and views. See
+ Alembic Utils at https://github.com/olirice/alembic_utils .
+
Replaceable objects present a problem in that in order to make incremental
changes to them, we have to refer to the whole definition at once.
If we need to add a new column to a view, for example, we have to drop