From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Sun, 17 Jan 2010 17:57:56 +0000 (+0000)
Subject: clarify shallow copy
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e1b22962e5672f67ca77806b1a8abfc49b661615;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

clarify shallow copy
---

diff --git a/lib/sqlalchemy/databases/postgres.py b/lib/sqlalchemy/databases/postgres.py
index cc963a6fd3..2ec820c739 100644
--- a/lib/sqlalchemy/databases/postgres.py
+++ b/lib/sqlalchemy/databases/postgres.py
@@ -233,7 +233,7 @@ class PGArray(sqltypes.MutableType, sqltypes.Concatenable, sqltypes.TypeEngine):
                           multi-dimensional arrays like `INTEGER[][]`, are constructed as `PGArray(Integer)`, not as
                           `PGArray(PGArray(Integer))` or such. The type mapping figures out on the fly
         :param mutable:   Defaults to True: specify whether lists passed to this class should be considered mutable.
-                          If so, then they are shallow-copied.
+                          If so, generic copy operations (typically used by the ORM) will shallow-copy values.
         """
         if isinstance(item_type, type):
             item_type = item_type()