From 0d9a42bcd686b4afa9d2da90e09b76284b50942a Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 27 Apr 2020 19:02:57 -0400 Subject: [PATCH] Add link to Alembic Utils as an example of replaceable objects. Change-Id: I9f8f423a363970814d2ca5fea2c0b2c35c34d19d References: #686 --- docs/build/cookbook.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/build/cookbook.rst b/docs/build/cookbook.rst index 83cabdb8..324c580c 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 `_ 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 -- 2.47.2