From: Jeff Widman Date: Wed, 4 Nov 2015 19:59:28 +0000 (+0000) Subject: Update links in SQLAlchemy docs that point to postgres docs to use 'devel' rather... X-Git-Tag: rel_1_0_10~51 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7a4d8dfd5419cfaa99d403e18f3b976e82e3eb65;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Update links in SQLAlchemy docs that point to postgres docs to use 'devel' rather than hardcoded version (cherry picked from commit 0d3ab3198a2863f28399a34a3bdbd1de0ca2530f) --- diff --git a/lib/sqlalchemy/dialects/postgresql/base.py b/lib/sqlalchemy/dialects/postgresql/base.py index fd5252567b..72b9fc1f43 100644 --- a/lib/sqlalchemy/dialects/postgresql/base.py +++ b/lib/sqlalchemy/dialects/postgresql/base.py @@ -102,7 +102,7 @@ via foreign key constraint, a decision must be made as to how the ``.schema`` is represented in those remote tables, in the case where that remote schema name is also a member of the current `Postgresql search path -`_. +`_. By default, the Postgresql dialect mimics the behavior encouraged by Postgresql's own ``pg_get_constraintdef()`` builtin procedure. This function @@ -506,7 +506,7 @@ dialect in conjunction with the :class:`.Table` construct: .. seealso:: `Postgresql CREATE TABLE options - `_ + `_ ENUM Types ----------