[Python-modules-commits] [sqlalchemy] 01/04: Import sqlalchemy_1.1.2+ds1.orig.tar.gz
Piotr Ożarowski
piotr at moszumanska.debian.org
Wed Oct 19 17:20:53 UTC 2016
This is an automated email from the git hooks/post-receive script.
piotr pushed a commit to branch master
in repository sqlalchemy.
commit c7782a7b2c28c48033ee9d6a1749dd48d10b6dc2
Author: Piotr Ożarowski <piotr at debian.org>
Date: Wed Oct 19 19:12:20 2016 +0200
Import sqlalchemy_1.1.2+ds1.orig.tar.gz
---
PKG-INFO | 2 +-
README.unittests.rst | 6 +-
doc/build/changelog/changelog_03.rst | 6 +-
doc/build/changelog/changelog_05.rst | 4 +-
doc/build/changelog/changelog_06.rst | 20 +--
doc/build/changelog/changelog_07.rst | 22 +--
doc/build/changelog/changelog_08.rst | 42 ++---
doc/build/changelog/changelog_09.rst | 36 ++---
doc/build/changelog/changelog_10.rst | 46 +++---
doc/build/changelog/changelog_11.rst | 63 +++++++-
doc/build/changelog/migration_06.rst | 22 +--
doc/build/changelog/migration_07.rst | 12 +-
doc/build/changelog/migration_08.rst | 16 +-
doc/build/changelog/migration_09.rst | 20 +--
doc/build/changelog/migration_10.rst | 32 ++--
doc/build/changelog/migration_11.rst | 2 +-
doc/build/conf.py | 4 +-
doc/build/core/constraints.rst | 6 +-
doc/build/core/custom_types.rst | 12 +-
doc/build/core/ddl.rst | 4 +-
doc/build/core/defaults.rst | 10 +-
doc/build/core/engines.rst | 6 +-
doc/build/core/reflection.rst | 2 +-
doc/build/core/sqlelement.rst | 15 +-
doc/build/core/tutorial.rst | 8 +-
doc/build/core/type_basics.rst | 2 +-
doc/build/dialects/index.rst | 4 +-
doc/build/faq/connections.rst | 2 +-
doc/build/glossary.rst | 6 +-
doc/build/orm/join_conditions.rst | 4 +-
doc/build/orm/session_transaction.rst | 2 +-
doc/build/orm/tutorial.rst | 6 +-
doc/build/orm/versioning.rst | 10 +-
examples/postgis/postgis.py | 4 +-
lib/sqlalchemy/__init__.py | 2 +-
lib/sqlalchemy/dialects/postgresql/array.py | 6 +-
lib/sqlalchemy/dialects/postgresql/base.py | 90 +++++------
lib/sqlalchemy/dialects/postgresql/dml.py | 2 +-
lib/sqlalchemy/dialects/postgresql/ext.py | 4 +-
lib/sqlalchemy/dialects/postgresql/hstore.py | 10 +-
lib/sqlalchemy/dialects/postgresql/json.py | 8 +-
lib/sqlalchemy/dialects/postgresql/psycopg2.py | 16 +-
lib/sqlalchemy/dialects/postgresql/ranges.py | 14 +-
.../dialects/type_migration_guidelines.txt | 4 +-
lib/sqlalchemy/engine/__init__.py | 4 +-
lib/sqlalchemy/engine/base.py | 6 +-
lib/sqlalchemy/engine/default.py | 2 +-
lib/sqlalchemy/engine/interfaces.py | 6 +-
lib/sqlalchemy/engine/reflection.py | 2 +-
lib/sqlalchemy/engine/result.py | 4 +-
lib/sqlalchemy/ext/baked.py | 16 +-
lib/sqlalchemy/ext/compiler.py | 2 +-
lib/sqlalchemy/ext/declarative/api.py | 3 -
lib/sqlalchemy/ext/indexable.py | 10 +-
lib/sqlalchemy/orm/loading.py | 42 +++--
lib/sqlalchemy/orm/query.py | 8 +-
lib/sqlalchemy/orm/strategies.py | 5 +-
lib/sqlalchemy/orm/strategy_options.py | 8 +
lib/sqlalchemy/pool.py | 2 +-
lib/sqlalchemy/sql/crud.py | 6 +-
lib/sqlalchemy/sql/ddl.py | 8 +-
lib/sqlalchemy/sql/dml.py | 4 +-
lib/sqlalchemy/sql/elements.py | 8 +-
lib/sqlalchemy/sql/functions.py | 2 +-
lib/sqlalchemy/sql/operators.py | 4 +-
lib/sqlalchemy/sql/schema.py | 18 ++-
lib/sqlalchemy/sql/selectable.py | 26 ++--
lib/sqlalchemy/sql/sqltypes.py | 25 +--
lib/sqlalchemy/sql/type_api.py | 4 +-
lib/sqlalchemy/testing/requirements.py | 4 +-
lib/sqlalchemy/testing/suite/test_results.py | 2 +-
lib/sqlalchemy/util/langhelpers.py | 3 +-
test/base/test_utils.py | 13 ++
test/dialect/postgresql/test_compiler.py | 22 +++
test/dialect/postgresql/test_on_conflict.py | 34 +++++
test/dialect/postgresql/test_types.py | 4 +-
test/engine/test_pool.py | 2 +-
test/ext/test_baked.py | 72 ++++++++-
test/orm/test_deferred.py | 48 ++++++
test/orm/test_eager_relations.py | 39 ++++-
test/orm/test_expire.py | 41 +++++
test/orm/test_lazy_relations.py | 2 +-
test/orm/test_merge.py | 2 +-
test/orm/test_subquery_relations.py | 2 +-
test/requirements.py | 2 +-
test/sql/test_generative.py | 4 +-
test/sql/test_insert.py | 170 ++++++++++-----------
test/sql/test_inspect.py | 2 +-
test/sql/test_metadata.py | 47 +++++-
test/sql/test_resultset.py | 2 +-
test/sql/test_returning.py | 2 +-
test/sql/test_update.py | 2 +-
92 files changed, 881 insertions(+), 479 deletions(-)
diff --git a/PKG-INFO b/PKG-INFO
index 844be3f..c5de66b 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: SQLAlchemy
-Version: 1.1.1
+Version: 1.1.2
Summary: Database Abstraction Library
Home-page: http://www.sqlalchemy.org
Author: Mike Bayer
diff --git a/README.unittests.rst b/README.unittests.rst
index 5aeba51..425cd4b 100644
--- a/README.unittests.rst
+++ b/README.unittests.rst
@@ -183,12 +183,12 @@ preexisting tables will interfere with the tests.
Several tests require alternate usernames or schemas to be present, which
are used to test dotted-name access scenarios. On some databases such
-as Oracle or Sybase, these are usernames, and others such as Postgresql
+as Oracle or Sybase, these are usernames, and others such as PostgreSQL
and MySQL they are schemas. The requirement applies to all backends
except SQLite and Firebird. The names are::
test_schema
- test_schema_2 (only used on Postgresql)
+ test_schema_2 (only used on PostgreSQL)
Please refer to your vendor documentation for the proper syntax to create
these namespaces - the database user must have permission to create and drop
@@ -335,6 +335,6 @@ For example, to run against sqlite, mysql, postgresql with four processes::
tox -e -- -n 4 --db sqlite --db postgresql --db mysql
-Each backend has a different scheme for setting up the database. Postgresql
+Each backend has a different scheme for setting up the database. PostgreSQL
still needs the "test_schema" and "test_schema_2" schemas present, as the
parallel databases are created using the base database as a "template".
diff --git a/doc/build/changelog/changelog_03.rst b/doc/build/changelog/changelog_03.rst
index 7c0a1af..349367c 100644
--- a/doc/build/changelog/changelog_03.rst
+++ b/doc/build/changelog/changelog_03.rst
@@ -878,7 +878,7 @@
preliminary support for unicode table names, column names and
SQL statements added, for databases which can support them.
- Works with sqlite and postgres so far. Mysql *mostly* works
+ Works with sqlite and postgres so far. MySQL *mostly* works
except the has_table() function does not work. Reflection
works too.
@@ -2701,7 +2701,7 @@
changed "for_update" parameter to accept False/True/"nowait"
and "read", the latter two of which are interpreted only by
- Oracle and Mysql
+ Oracle and MySQL
.. change::
:tags: construction, sql
@@ -2753,7 +2753,7 @@
:tickets:
a wide refactoring to "attribute loader" and "options" architectures.
- ColumnProperty and PropertyLoader define their loading behaivor via switchable
+ ColumnProperty and PropertyLoader define their loading behavior via switchable
"strategies", and MapperOptions no longer use mapper/property copying
in order to function; they are instead propagated via QueryContext
and SelectionContext objects at query/instances time.
diff --git a/doc/build/changelog/changelog_05.rst b/doc/build/changelog/changelog_05.rst
index f612cee..5bcfd5f 100644
--- a/doc/build/changelog/changelog_05.rst
+++ b/doc/build/changelog/changelog_05.rst
@@ -783,7 +783,7 @@
itself differently to some MapperExtensions.
The change also affects the internal attribute API, but not
- the AttributeExtension interface nor any of the publically
+ the AttributeExtension interface nor any of the publicly
documented attribute functions.
- The unit of work no longer genererates a graph of "dependency"
@@ -1461,7 +1461,7 @@
Query.from_self() as well as query.subquery() both disable
the rendering of eager joins inside the subquery produced.
- The "disable all eager joins" feature is available publically
+ The "disable all eager joins" feature is available publicly
via a new query.enable_eagerloads() generative.
.. change::
diff --git a/doc/build/changelog/changelog_06.rst b/doc/build/changelog/changelog_06.rst
index 168dac9..d1c7fe5 100644
--- a/doc/build/changelog/changelog_06.rst
+++ b/doc/build/changelog/changelog_06.rst
@@ -543,7 +543,7 @@
of the auto-generated sequence of a SERIAL column,
which currently only occurs if implicit_returning=False,
now accommodates if the table + column name is greater
- than 63 characters using the same logic Postgresql uses.
+ than 63 characters using the same logic PostgreSQL uses.
.. change::
:tags: postgresql
@@ -2850,7 +2850,7 @@
:tags: postgresql
:tickets: 1071
- Postgresql now reflects sequence names associated with
+ PostgreSQL now reflects sequence names associated with
SERIAL columns correctly, after the name of the sequence
has been changed. Thanks to Kumar McMillan for the patch.
@@ -2873,7 +2873,7 @@
:tags: postgresql
:tickets: 1769
- Postgresql reflects the name of primary key constraints,
+ PostgreSQL reflects the name of primary key constraints,
if one exists.
.. change::
@@ -3462,7 +3462,7 @@
as well as the adaptation of the Python operator into
a SQL operator, based on the full left/right/operator
of the given expression. In particular
- the date/time/interval system created for Postgresql
+ the date/time/interval system created for PostgreSQL
EXTRACT in has now been generalized into
the type system. The previous behavior which often
occurred of an expression "column + literal" forcing
@@ -4259,7 +4259,7 @@
returning() support is native to insert(), update(),
delete(). Implementations of varying levels of
- functionality exist for Postgresql, Firebird, MSSQL and
+ functionality exist for PostgreSQL, Firebird, MSSQL and
Oracle. returning() can be called explicitly with column
expressions which are then returned in the resultset,
usually via fetchone() or first().
@@ -4280,7 +4280,7 @@
another will now be grouped with parenthesis - previously,
the first compound element in the list would not be grouped,
as SQLite doesn't like a statement to start with
- parenthesis. However, Postgresql in particular has
+ parenthesis. However, PostgreSQL in particular has
precedence rules regarding INTERSECT, and it is
more consistent for parenthesis to be applied equally
to all sub-elements. So now, the workaround for SQLite
@@ -4586,7 +4586,7 @@
The "start" and "increment" attributes on Sequence now
generate "START WITH" and "INCREMENT BY" by default,
- on Oracle and Postgresql. Firebird doesn't support
+ on Oracle and PostgreSQL. Firebird doesn't support
these keywords right now.
.. change::
@@ -5227,7 +5227,7 @@
:tickets:
The construction of types within dialects has been totally
- overhauled. Dialects now define publically available types
+ overhauled. Dialects now define publicly available types
as UPPERCASE names exclusively, and internal implementation
types using underscore identifiers (i.e. are private).
The system by which types are expressed in SQL and DDL
@@ -5279,7 +5279,7 @@
optimized, resulting in varying speed improvements:
Unicode, PickleType, Interval, TypeDecorator, Binary.
Also the following dbapi-specific implementations have been improved:
- Time, Date and DateTime on Sqlite, ARRAY on Postgresql,
+ Time, Date and DateTime on Sqlite, ARRAY on PostgreSQL,
Time on MySQL, Numeric(as_decimal=False) on MySQL, oursql and
pypostgresql, DateTime on cx_oracle and LOB-based types on cx_oracle.
@@ -5332,7 +5332,7 @@
PickleType now uses == for comparison of values when
mutable=True, unless the "comparator" argument with a
- comparsion function is specified to the type. Objects
+ comparison function is specified to the type. Objects
being pickled will be compared based on identity (which
defeats the purpose of mutable=True) if __eq__() is not
overridden or a comparison function is not provided.
diff --git a/doc/build/changelog/changelog_07.rst b/doc/build/changelog/changelog_07.rst
index fa952f0..a77945f 100644
--- a/doc/build/changelog/changelog_07.rst
+++ b/doc/build/changelog/changelog_07.rst
@@ -88,7 +88,7 @@
:tickets: 2676
:versions: 0.8.0
- Added support for Postgresql's traditional SUBSTRING
+ Added support for PostgreSQL's traditional SUBSTRING
function syntax, renders as "SUBSTRING(x FROM y FOR z)"
when regular ``func.substring()`` is used.
Courtesy Gunnlaugur Þór Briem.
@@ -885,7 +885,7 @@
:tickets: 2445
Added new for_update/with_lockmode()
- options for Postgresql: for_update="read"/
+ options for PostgreSQL: for_update="read"/
with_lockmode("read"),
for_update="read_nowait"/
with_lockmode("read_nowait").
@@ -1873,7 +1873,7 @@
The update() construct can now accommodate
multiple tables in the WHERE clause, which will
render an "UPDATE..FROM" construct, recognized by
- Postgresql and MSSQL. When compiled on MySQL,
+ PostgreSQL and MSSQL. When compiled on MySQL,
will instead generate "UPDATE t1, t2, ..". MySQL
additionally can render against multiple tables in the
SET clause, if Column objects are used as keys
@@ -1968,7 +1968,7 @@
:tickets: 1679
a "has_schema" method has been implemented
- on dialect, but only works on Postgresql so far.
+ on dialect, but only works on PostgreSQL so far.
Courtesy Manlio Perillo.
.. change::
@@ -2025,7 +2025,7 @@
:tags: postgresql, bug
:tickets: 2311
- Postgresql dialect memoizes that an ENUM of a
+ PostgreSQL dialect memoizes that an ENUM of a
particular name was processed
during a create/drop sequence. This allows
a create/drop sequence to work without any
@@ -3696,7 +3696,7 @@
:tickets: 2081
REAL has been added to the core types. Supported
- by Postgresql, SQL Server, MySQL, SQLite. Note
+ by PostgreSQL, SQL Server, MySQL, SQLite. Note
that the SQL Server and MySQL versions, which
add extra arguments, are also still available
from those dialects.
@@ -4348,7 +4348,7 @@
:tickets: 1069
Query.distinct() now accepts column expressions
- as \*args, interpreted by the Postgresql dialect
+ as \*args, interpreted by the PostgreSQL dialect
as DISTINCT ON (<expr>).
.. change::
@@ -4448,7 +4448,7 @@
:tickets: 1069
select.distinct() now accepts column expressions
- as \*args, interpreted by the Postgresql dialect
+ as \*args, interpreted by the PostgreSQL dialect
as DISTINCT ON (<expr>). Note this was already
available via passing a list to the `distinct`
keyword argument to select().
@@ -4531,7 +4531,7 @@
"isolation_level" argument, sets transaction isolation
level for that connection only until returned to the
connection pool, for those backends which support it
- (SQLite, Postgresql)
+ (SQLite, PostgreSQL)
.. change::
:tags: sql
@@ -4648,7 +4648,7 @@
of the auto-generated sequence of a SERIAL column,
which currently only occurs if implicit_returning=False,
now accommodates if the table + column name is greater
- than 63 characters using the same logic Postgresql uses. (also in 0.6.7)
+ than 63 characters using the same logic PostgreSQL uses. (also in 0.6.7)
.. change::
:tags: postgresql
@@ -4668,7 +4668,7 @@
'unbounded'. This also occurs for the VARBINARY type..
This behavior makes these types more closely compatible
- with Postgresql's VARCHAR type which is similarly unbounded
+ with PostgreSQL's VARCHAR type which is similarly unbounded
when no length is specified.
.. change::
diff --git a/doc/build/changelog/changelog_08.rst b/doc/build/changelog/changelog_08.rst
index ddf6be5..6eb5830 100644
--- a/doc/build/changelog/changelog_08.rst
+++ b/doc/build/changelog/changelog_08.rst
@@ -197,7 +197,7 @@
:versions: 0.9.4
Fixed regression caused by release 0.8.5 / 0.9.3's compatibility
- enhancements where index reflection on Postgresql versions specific
+ enhancements where index reflection on PostgreSQL versions specific
to only the 8.1, 8.2 series again
broke, surrounding the ever problematic int2vector type. While
int2vector supports array operations as of 8.1, apparently it only
@@ -284,8 +284,8 @@
:tags: postgresql, bug
:versions: 0.9.3
- Support has been improved for Postgresql reflection behavior on very old
- (pre 8.1) versions of Postgresql, and potentially other PG engines
+ Support has been improved for PostgreSQL reflection behavior on very old
+ (pre 8.1) versions of PostgreSQL, and potentially other PG engines
such as Redshift (assuming Redshift reports the version as < 8.1).
The query for "indexes" as well as "primary keys" relies upon inspecting
a so-called "int2vector" datatype, which refuses to coerce to an array
@@ -351,10 +351,10 @@
:tickets: 2291
:versions: 0.9.3
- Revised this very old issue where the Postgresql "get primary key"
+ Revised this very old issue where the PostgreSQL "get primary key"
reflection query were updated to take into account primary key constraints
that were renamed; the newer query fails on very old versions of
- Postgresql such as version 7, so the old query is restored in those cases
+ PostgreSQL such as version 7, so the old query is restored in those cases
when server_version_info < (8, 0) is detected.
.. change::
@@ -798,8 +798,8 @@
:tickets: 2819
:versions: 0.9.0b1
- Fixed bug where Postgresql version strings that had a prefix preceding
- the words "Postgresql" or "EnterpriseDB" would not parse.
+ Fixed bug where PostgreSQL version strings that had a prefix preceding
+ the words "PostgreSQL" or "EnterpriseDB" would not parse.
Courtesy Scott Schaefer.
.. change::
@@ -834,7 +834,7 @@
Added a new flag ``system=True`` to :class:`.Column`, which marks
the column as a "system" column which is automatically made present
- by the database (such as Postgresql ``oid`` or ``xmin``). The
+ by the database (such as PostgreSQL ``oid`` or ``xmin``). The
column will be omitted from the ``CREATE TABLE`` statement but will
otherwise be available for querying. In addition, the
:class:`.CreateColumn` construct can be appled to a custom
@@ -942,7 +942,7 @@
form of a some expressions when referring to the ``.c`` collection
on a ``select()`` construct, but the ``str()`` form isn't available
since the element relies on dialect-specific compilation constructs,
- notably the ``__getitem__()`` operator as used with a Postgresql
+ notably the ``__getitem__()`` operator as used with a PostgreSQL
``ARRAY`` element. The fix also adds a new exception class
:exc:`.UnsupportedCompilationError` which is raised in those cases
where a compiler is asked to compile something it doesn't know
@@ -1069,7 +1069,7 @@
:versions: 0.9.0b1
The behavior of :func:`.extract` has been simplified on the
- Postgresql dialect to no longer inject a hardcoded ``::timestamp``
+ PostgreSQL dialect to no longer inject a hardcoded ``::timestamp``
or similar cast into the given expression, as this interfered
with types such as timezone-aware datetimes, but also
does not appear to be at all necessary with modern versions
@@ -1103,7 +1103,7 @@
:versions: 0.9.0b1
Fixed bug where the order of columns in a multi-column
- Postgresql index would be reflected in the wrong order.
+ PostgreSQL index would be reflected in the wrong order.
Courtesy Roman Podolyaka.
.. change::
@@ -1167,7 +1167,7 @@
:tags: feature, postgresql
:versions: 0.9.0b1
- Support for Postgresql 9.2 range types has been added.
+ Support for PostgreSQL 9.2 range types has been added.
Currently, no type translation is provided, so works
directly with strings or psycopg2 2.5 range extension types
at the moment. Patch courtesy Chris Withers.
@@ -1463,7 +1463,7 @@
:tags: bug, postgresql
:tickets: 2681
- The operators for the Postgresql ARRAY type supports
+ The operators for the PostgreSQL ARRAY type supports
input types of sets, generators, etc. even when
a dimension is not specified, by turning the given
iterable into a collection unconditionally.
@@ -1872,7 +1872,7 @@
is now copied in all cases when :meth:`.Table.tometadata` happens,
and if ``inherit_schema=True``, the type will take on the new
schema name passed to the method. The ``schema`` is important
- when used with the Postgresql backend, as the type results in
+ when used with the PostgreSQL backend, as the type results in
a ``CREATE TYPE`` statement.
.. change::
@@ -2153,7 +2153,7 @@
The :class:`.Insert` construct now supports multi-valued inserts,
that is, an INSERT that renders like
"INSERT INTO table VALUES (...), (...), ...".
- Supported by Postgresql, SQLite, and MySQL.
+ Supported by PostgreSQL, SQLite, and MySQL.
Big thanks to Idan Kamara for doing the legwork on this one.
.. seealso::
@@ -2272,7 +2272,7 @@
:tags: postgresql, feature
:tickets: 2606
- :class:`.HSTORE` is now available in the Postgresql dialect.
+ :class:`.HSTORE` is now available in the PostgreSQL dialect.
Will also use psycopg2's extensions if available. Courtesy
Audrius Kažukauskas.
@@ -3189,7 +3189,7 @@
to augment bind- and result- behavior at the
SQL level, as opposed to in the Python level.
Allows for schemes like transparent encryption/
- decryption, usage of Postgis functions, etc.
+ decryption, usage of PostGIS functions, etc.
.. change::
:tags: feature, sql
@@ -3199,7 +3199,7 @@
the `getitem` operator, i.e. the bracket
operator in Python. This is used at first
to provide index and slice behavior to the
- Postgresql ARRAY type, and also provides a hook
+ PostgreSQL ARRAY type, and also provides a hook
for end-user definition of custom __getitem__
schemes which can be applied at the type
level as well as within ORM-level custom
@@ -3237,7 +3237,7 @@
String types. When present, renders as
COLLATE <collation>. This to support the
COLLATE keyword now supported by several
- databases including MySQL, SQLite, and Postgresql.
+ databases including MySQL, SQLite, and PostgreSQL.
.. change::
:tags: change, sql
@@ -3603,7 +3603,7 @@
:tags: postgresql, feature
:tickets: 2506
- Added support for the Postgresql ONLY
+ Added support for the PostgreSQL ONLY
keyword, which can appear corresponding to a
table in a SELECT, UPDATE, or DELETE statement.
The phrase is established using with_hint().
@@ -3614,7 +3614,7 @@
:tickets:
The "ischema_names" dictionary of the
- Postgresql dialect is "unofficially" customizable.
+ PostgreSQL dialect is "unofficially" customizable.
Meaning, new types such as PostGIS types can
be added into this dictionary, and the PG type
reflection code should be able to handle simple
diff --git a/doc/build/changelog/changelog_09.rst b/doc/build/changelog/changelog_09.rst
index 0084275..c912387 100644
--- a/doc/build/changelog/changelog_09.rst
+++ b/doc/build/changelog/changelog_09.rst
@@ -194,7 +194,7 @@
:pullreq: bitbucket:45
:versions: 1.0.0b1
- Added support for the ``CONCURRENTLY`` keyword with Postgresql
+ Added support for the ``CONCURRENTLY`` keyword with PostgreSQL
indexes, established using ``postgresql_concurrently``. Pull
request courtesy Iuri de Silvio.
@@ -312,7 +312,7 @@
:tickets: 2940
:versions: 1.0.0b1
- Repaired support for Postgresql UUID types in conjunction with
+ Repaired support for PostgreSQL UUID types in conjunction with
the ARRAY type when using psycopg2. The psycopg2 dialect now
employs use of the psycopg2.extras.register_uuid() hook
so that UUID values are always passed to/from the DBAPI as
@@ -331,7 +331,7 @@
additionally, the newly added psycopg2 extension
``extras.register_default_jsonb`` is used to establish a JSON
deserializer passed to the dialect via the ``json_deserializer``
- argument. Also repaired the Postgresql integration tests which
+ argument. Also repaired the PostgreSQL integration tests which
weren't actually round-tripping the JSONB type as opposed to the
JSON type. Pull request courtesy Mateusz Susik.
@@ -374,7 +374,7 @@
:versions: 1.0.0b1
:tickets: 3174
- Fixed bug where Postgresql dialect would fail to render an
+ Fixed bug where PostgreSQL dialect would fail to render an
expression in an :class:`.Index` that did not correspond directly
to a table-bound column; typically when a :func:`.text` construct
was one of the expressions within the index; or could misinterpret the
@@ -770,7 +770,7 @@
:versions: 1.0.0b1
:tickets: 3159
- Fixed bug where Postgresql JSON type was not able to persist or
+ Fixed bug where PostgreSQL JSON type was not able to persist or
otherwise render a SQL NULL column value, rather than a JSON-encoded
``'null'``. To support this case, changes are as follows:
@@ -891,7 +891,7 @@
then force all :class:`.Boolean` and :class:`.Enum` types to
require names as well, as these implicitly create a
constraint, even if the ultimate target backend were one that does
- not require generation of the constraint such as Postgresql.
+ not require generation of the constraint such as PostgreSQL.
The mechanics of naming conventions for these particular
constraints has been reorganized such that the naming
determination is done at DDL compile time, rather than at
@@ -990,7 +990,7 @@
:versions: 1.0.0b1
:pullreq: github:101
- Added support for Postgresql JSONB via :class:`.JSONB`. Pull request
+ Added support for PostgreSQL JSONB via :class:`.JSONB`. Pull request
courtesy Damian Dimmich.
.. change::
@@ -1048,7 +1048,7 @@
Fixed bug when the declarative ``__abstract__`` flag was not being
distinguished for when it was actually the value ``False``.
- The ``__abstract__`` flag needs to acutally evaluate to a True
+ The ``__abstract__`` flag needs to actually evaluate to a True
value at the level being tested.
.. changelog::
@@ -1103,7 +1103,7 @@
:tickets: 3002
:versions: 1.0.0b1
- Added a new type :class:`.postgresql.OID` to the Postgresql dialect.
+ Added a new type :class:`.postgresql.OID` to the PostgreSQL dialect.
While "oid" is generally a private type within PG that is not exposed
in modern versions, there are some PG use cases such as large object
support where these types might be exposed, as well as within some
@@ -1231,11 +1231,11 @@
:pullreq: bitbucket:18
:versions: 1.0.0b1
- Added a new flag :paramref:`.ARRAY.zero_indexes` to the Postgresql
+ Added a new flag :paramref:`.ARRAY.zero_indexes` to the PostgreSQL
:class:`.ARRAY` type. When set to ``True``, a value of one will be
added to all array index values before passing to the database, allowing
better interoperability between Python style zero-based indexes and
- Postgresql one-based indexes. Pull request courtesy Alexey Terentev.
+ PostgreSQL one-based indexes. Pull request courtesy Alexey Terentev.
.. change::
:tags: bug, engine
@@ -1852,7 +1852,7 @@
fully usable within declarative relationship configuration, as its
string classname would not be available in the registry of classnames
at mapper configuration time. The class now explicitly adds itself
- to the class regsitry, and additionally both :class:`.AbstractConcreteBase`
+ to the class registry, and additionally both :class:`.AbstractConcreteBase`
as well as :class:`.ConcreteBase` set themselves up *before* mappers
are configured within the :func:`.configure_mappers` setup, using
the new :meth:`.MapperEvents.before_configured` event.
@@ -1957,7 +1957,7 @@
Added a new dialect-level argument ``postgresql_ignore_search_path``;
this argument is accepted by both the :class:`.Table` constructor
as well as by the :meth:`.MetaData.reflect` method. When in use
- against Postgresql, a foreign-key referenced table which specifies
+ against PostgreSQL, a foreign-key referenced table which specifies
a remote schema name will retain that schema name even if the name
is present in the ``search_path``; the default behavior since 0.7.3
has been that schemas present in ``search_path`` would not be copied
@@ -2500,7 +2500,7 @@
:tickets: 2581
:pullreq: github:50
- Support for Postgresql JSON has been added, using the new
+ Support for PostgreSQL JSON has been added, using the new
:class:`.JSON` type. Huge thanks to Nathan Rice for
implementing and testing this.
@@ -2550,7 +2550,7 @@
:tags: feature, postgresql
:pullreq: bitbucket:8
- Added support for Postgresql TSVECTOR via the
+ Added support for PostgreSQL TSVECTOR via the
:class:`.postgresql.TSVECTOR` type. Pull request courtesy
Noufal Ibrahim.
@@ -2825,8 +2825,8 @@
:tags: feature, sql, postgresql, mysql
:tickets: 2183
- The Postgresql and MySQL dialects now support reflection/inspection
- of foreign key options, including ON UPDATE, ON DELETE. Postgresql
+ The PostgreSQL and MySQL dialects now support reflection/inspection
+ of foreign key options, including ON UPDATE, ON DELETE. PostgreSQL
also reflects MATCH, DEFERRABLE, and INITIALLY. Coutesy ijl.
.. change::
@@ -2936,7 +2936,7 @@
Added support for rendering ``SMALLSERIAL`` when a :class:`.SmallInteger`
type is used on a primary key autoincrement column, based on server
- version detection of Postgresql version 9.2 or greater.
+ version detection of PostgreSQL version 9.2 or greater.
.. change::
:tags: feature, mysql
diff --git a/doc/build/changelog/changelog_10.rst b/doc/build/changelog/changelog_10.rst
index 8fd6b1d..8a061cd 100644
--- a/doc/build/changelog/changelog_10.rst
+++ b/doc/build/changelog/changelog_10.rst
@@ -133,7 +133,7 @@
:versions: 1.1.0b3
Fixed bug whereby :class:`.TypeDecorator` and :class:`.Variant`
- types were not deeply inspected enough by the Postgresql dialect
+ types were not deeply inspected enough by the PostgreSQL dialect
to determine if SMALLSERIAL or BIGSERIAL needed to be rendered
rather than SERIAL.
@@ -384,7 +384,7 @@
Fixed bug in :func:`.expression.text` construct where a double-colon
expression would not escape properly, e.g. ``some\:\:expr``, as is most
- commonly required when rendering Postgresql-style CAST expressions.
+ commonly required when rendering PostgreSQL-style CAST expressions.
.. change::
:tags: bug, sql
@@ -436,7 +436,7 @@
provided by :class:`.Session` and :class:`.Connection`, and taking
place for operations such as a failure on "RELEASE SAVEPOINT".
Previously, the fix was only in place for a specific path within
- the ORM flush/commit process; it now takes place for all transational
+ the ORM flush/commit process; it now takes place for all transactional
context managers as well.
.. change::
@@ -627,7 +627,7 @@
Fixed bug where CREATE TABLE with a no-column table, but a constraint
such as a CHECK constraint would render an erroneous comma in the
- definition; this scenario can occur such as with a Postgresql
+ definition; this scenario can occur such as with a PostgreSQL
INHERITS table that has no columns of its own.
.. change::
@@ -645,7 +645,7 @@
:tickets: 3573
- Fixed issue where the "FOR UPDATE OF" Postgresql-specific SELECT
+ Fixed issue where the "FOR UPDATE OF" PostgreSQL-specific SELECT
modifier would fail if the referred table had a schema qualifier;
PG needs the schema name to be omitted. Pull request courtesy
Diana Clarke.
@@ -782,7 +782,7 @@
Fixed regression in 1.0 where new feature of using "executemany"
for UPDATE statements in the ORM (e.g. :ref:`feature_updatemany`)
- would break on Postgresql and other RETURNING backends
+ would break on PostgreSQL and other RETURNING backends
when using server-side version generation
schemes, as the server side value is retrieved via RETURNING which
is not supported with executemany.
@@ -878,11 +878,11 @@
:pullreq: github:190
- An adjustment to the new Postgresql feature of reflecting storage
+ An adjustment to the new PostgreSQL feature of reflecting storage
options and USING of :ticket:`3455` released in 1.0.6,
- to disable the feature for Postgresql versions < 8.2 where the
+ to disable the feature for PostgreSQL versions < 8.2 where the
``reloptions`` column is not provided; this allows Amazon Redshift
- to again work as it is based on an 8.0.x version of Postgresql.
+ to again work as it is based on an 8.0.x version of PostgreSQL.
Fix courtesy Pete Hollobon.
@@ -967,7 +967,7 @@
:pullreq: github:186
Added support for the MINVALUE, MAXVALUE, NO MINVALUE, NO MAXVALUE,
- and CYCLE arguments for CREATE SEQUENCE as supported by Postgresql
+ and CYCLE arguments for CREATE SEQUENCE as supported by PostgreSQL
and Oracle. Pull request courtesy jakeogh.
.. change::
@@ -1552,7 +1552,7 @@
label name for all backends, as described in :ref:`migration_1068`,
even though 1.0 includes a rewrite of this logic as part of
:ticket:`2992`. As far
- as emitting GROUP BY against a simple label, even Postgresql has
+ as emitting GROUP BY against a simple label, even PostgreSQL has
cases where it will raise an error even though the label to group
on should be apparent, so it is clear that GROUP BY should never
be rendered in this way automatically.
@@ -1820,9 +1820,9 @@
:tickets: 3343
Fixed bug where updated PG index reflection as a result of
- :ticket:`3184` would cause index operations to fail on Postgresql
+ :ticket:`3184` would cause index operations to fail on PostgreSQL
versions 8.4 and earlier. The enhancements are now
- disabled when using an older version of Postgresql.
+ disabled when using an older version of PostgreSQL.
.. change::
:tags: bug, sql
@@ -2003,7 +2003,7 @@
:tags: bug, postgresql
:tickets: 3319
- The Postgresql :class:`.postgresql.ENUM` type will emit a
+ The PostgreSQL :class:`.postgresql.ENUM` type will emit a
DROP TYPE instruction when a plain ``table.drop()`` is called,
assuming the object is not associated directly with a
:class:`.MetaData` object. In order to accommodate the use case of
@@ -2011,7 +2011,7 @@
be associated directly with the :class:`.MetaData` object; in this
case the type will only be created at the metadata level, or if
created directly. The rules for create/drop of
- Postgresql enumerated types have been highly reworked in general.
+ PostgreSQL enumerated types have been highly reworked in general.
.. seealso::
@@ -2494,7 +2494,7 @@
``pg_catalog.pg_table_is_visible(c.oid)``, rather than testing
for an exact schema match, when the schema name is None; this
so that the method will also illustrate that temporary tables
- are present. Note that this is a behavioral change, as Postgresql
+ are present. Note that this is a behavioral change, as PostgreSQL
allows a non-temporary table to silently overwrite an existing
temporary table of the same name, so this changes the behavior
of ``checkfirst`` in that unusual scenario.
@@ -2757,13 +2757,13 @@
The :class:`.UniqueConstraint` construct is now included when
reflecting a :class:`.Table` object, for databases where this
is applicable. In order to achieve this
- with sufficient accuracy, MySQL and Postgresql now contain features
+ with sufficient accuracy, MySQL and PostgreSQL now contain features
that correct for the duplication of indexes and unique constraints
when reflecting tables, indexes, and constraints.
In the case of MySQL, there is not actually a "unique constraint"
concept independent of a "unique index", so for this backend
:class:`.UniqueConstraint` continues to remain non-present for a
- reflected :class:`.Table`. For Postgresql, the query used to
+ reflected :class:`.Table`. For PostgreSQL, the query used to
detect indexes against ``pg_index`` has been improved to check for
the same construct in ``pg_constraint``, and the implicitly
constructed unique index is not included with a
@@ -2772,7 +2772,7 @@
In both cases, the :meth:`.Inspector.get_indexes` and the
:meth:`.Inspector.get_unique_constraints` methods return both
constructs individually, but include a new token
- ``duplicates_constraint`` in the case of Postgresql or
+ ``duplicates_constraint`` in the case of PostgreSQL or
``duplicates_index`` in the case
of MySQL to indicate when this condition is detected.
Pull request courtesy Johannes Erdfelt.
@@ -2786,7 +2786,7 @@
:pullreq: github:134
Added support for the FILTER keyword as applied to aggregate
- functions, supported by Postgresql 9.4. Pull request
+ functions, supported by PostgreSQL 9.4. Pull request
courtesy Ilja Everilä.
.. seealso::
@@ -2856,7 +2856,7 @@
for a non-nullable or ``ondelete="SET NULL"`` for a nullable set
of columns, the argument ``passive_deletes=True`` is also added to the
relationship. Note that not all backends support reflection of
- ondelete, but backends that do include Postgresql and MySQL.
+ ondelete, but backends that do include PostgreSQL and MySQL.
.. change::
:tags: feature, sql
@@ -2907,7 +2907,7 @@
and foreign tables, as well as support for materialized views
within :meth:`.Inspector.get_view_names`, and a new method
:meth:`.PGInspector.get_foreign_table_names` available on the
- Postgresql version of :class:`.Inspector`. Pull request courtesy
+ PostgreSQL version of :class:`.Inspector`. Pull request courtesy
Rodrigo Menezes.
.. seealso::
@@ -3252,7 +3252,7 @@
:pullreq: github:126
Added new method :meth:`.PGInspector.get_enums`, when using the
- inspector for Postgresql will provide a list of ENUM types.
+ inspector for PostgreSQL will provide a list of ENUM types.
Pull request courtesy Ilya Pekelny.
.. change::
diff --git a/doc/build/changelog/changelog_11.rst b/doc/build/changelog/changelog_11.rst
index a8d73bb..ea14432 100644
--- a/doc/build/changelog/changelog_11.rst
+++ b/doc/build/changelog/changelog_11.rst
@@ -19,6 +19,63 @@
:start-line: 5
.. changelog::
+ :version: 1.1.2
+ :released: October 17, 2016
+
+ .. change::
+ :tags: bug, sql
+ :tickets: 3823
+
+ Fixed a regression caused by a newly added function that performs the
+ "wrap callable" function of sql :class:`.DefaultGenerator` objects,
+ an attribute error raised for ``__module__`` when the default callable
+ was a ``functools.partial`` or other object that doesn't have a
+ ``__module__`` attribute.
+
+ .. change::
+ :tags: bug, orm
+ :tickets: 3824
+
+ Fixed bug involving the rule to disable a joined collection eager
+ loader on the other side of a many-to-one lazy loader, first added
+ in :ticket:`1495`, where the rule would fail if the parent object
+ had some other lazyloader-bound query options associated with it.
+
+ .. change::
+ :tags: bug, orm
+ :tickets: 3822
+
+ Fixed self-referential entity, deferred column loading issue in a
+ similar style as that of :ticket:`3431`, :ticket:`3811` where an entity
+ is present in multiple positions within the row due to self-referential
+ eager loading; when the deferred loader only applies to one of the
+ paths, the "present" column loader will now override the deferred non-
+ load for that entity regardless of row ordering.
+
+ .. change::
+ :tags: bug, sql, postgresql
+ :tickets: 3827
+
+ Fixed regression in :class:`.Enum` type where event handlers were not
+ transferred in the case of the type object being copied, due to a
+ conflicting copy() method added as part of :ticket:`3250`. This copy
+ occurs normally in situations when the column is copied, such as
+ in tometadata() or when using declarative mixins with columns. The
+ event handler not being present would impact the constraint being
+ created for a non-native enumerated type, but more critically the
+ ENUM object on the PostgreSQL backend.
+
+
+ .. change::
+ :tags: bug, postgresql, sql
+ :tickets: 3828
+
+ Changed the naming convention used when generating bound parameters
+ for a multi-VALUES insert statement, so that the numbered parameter
+ names don't conflict with the anonymized parameters of a WHERE clause,
+ as is now common in a PostgreSQL ON CONFLICT construct.
+
+.. changelog::
:version: 1.1.1
:released: October 7, 2016
@@ -132,10 +189,10 @@
:tags: bug, sql, postgresql
:tickets: 3806
- Added compiler-level flags used by Postgresql to place additional
+ Added compiler-level flags used by PostgreSQL to place additional
parenthesis than would normally be generated by precedence rules
around operations involving JSON, HSTORE indexing operators as well as
- within their operands since it has been observed that Postgresql's
+ within their operands since it has been observed that PostgreSQL's
precedence rules for at least the HSTORE indexing operator is not
consistent between 9.4 and 9.5.
@@ -259,7 +316,7 @@
Fixed regression in JSON datatypes where the "literal processor" for
a JSON index value would not be invoked. The native String and Integer
datatypes are now called upon from within the JSONIndexType
- and JSONPathType. This is applied to the generic, Postgresql, and
+ and JSONPathType. This is applied to the generic, PostgreSQL, and
MySQL JSON types and also has a dependency on :ticket:`3766`.
.. change::
diff --git a/doc/build/changelog/migration_06.rst b/doc/build/changelog/migration_06.rst
... 3381 lines suppressed ...
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/packages/sqlalchemy.git
More information about the Python-modules-commits
mailing list