summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2013-04-22 17:08:02 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2013-04-22 17:08:02 -0400
commitd2f8c83e25ea7abb49315c30518f6415b497f1a7 (patch)
tree38710ed38b7e3924084680431262db5e4a9ff1e2 /doc
parent422f4718715ad89346f42caf03bdd2ed745e5a23 (diff)
downloadsqlalchemy-d2f8c83e25ea7abb49315c30518f6415b497f1a7.tar.gz
- change to [ticket:2681], pre-coerce the array to list
unconditonally instead so that it works in all cases.
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/changelog_08.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst
index b64a188f7..489cad582 100644
--- a/doc/build/changelog/changelog_08.rst
+++ b/doc/build/changelog/changelog_08.rst
@@ -11,12 +11,9 @@
:tickets: 2681
The operators for the Postgresql ARRAY type supports
- input types of sets, generators, etc. but only when a dimension
- is specified for the ARRAY; otherwise, the dialect
- needs to peek inside of "arr[0]" to guess how many
- dimensions are in use. If this occurs with a non
- list/tuple type, the error message is now informative
- and directs to specify a dimension for the ARRAY.
+ input types of sets, generators, etc. even when
+ a dimension is not specified, by turning the given
+ iterable into a collection unconditionally.
.. change::
:tags: bug, mysql