sqlalchemy-commits — SVN commits logged to this list

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - try one more test, then we're likely going to give up on cx_Oracle

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/bfaef1eaf54e/
Changeset:   bfaef1eaf54e
Branch:      master
User:        zzzeek
Date:        2017-04-12 19:28:05+00:00
Summary:     - try one more test, then we're likely going to give up on cx_Oracle

Change-Id: I7f9a1265664b0368ee7a771d01c7ca1612156d1f

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - move a few memusage tests out of "backend". something is up w/ cx_Oracle

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b1f8d46fca95/
Changeset:   b1f8d46fca95
Branch:      master
User:        zzzeek
Date:        2017-04-12 19:15:16+00:00
Summary:     - move a few memusage tests out of "backend".  something is up w/ cx_Oracle
when the suite runs, such as a background thread or something like that,
which is affecting these tests a bit.

Change-Id: I52d50a44778ec1eecb8e335ae59b1a4773e80a79

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Warn on _compiled_cache growth

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/cef4e5ff38dc/
Changeset:   cef4e5ff38dc
Branch:      master
User:        zzzeek
Date:        2017-04-12 16:53:40+00:00
Summary:     Warn on _compiled_cache growth

Added warnings to the LRU "compiled cache" used by the :class:`.Mapper`
(and ultimately will be for other ORM-based LRU caches) such that
when the cache starts hitting its size limits, the application will
emit a warning that this is a performance-degrading situation that
may require attention.   The LRU caches can reach their size limits
primarily if an application is making use of an unbounded number
of :class:`.Engine` objects, which is an antipattern.  Otherwise,
this may suggest an issue that should be brought to the SQLAlchemy
developer's attention.

Additionally, adjusted the test_memusage algorithm again as the
previous one could still allow a growing memory size to be missed.

Change-Id: I020d1ceafb7a08f6addfa990a1e7acd09f933240

Affected #:  6 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Set up base ARRAY to be compatible with postgresql.ARRAY.

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1b463058e328/
Changeset:   1b463058e328
Branch:      master
User:        zzzeek
Date:        2017-04-11 14:49:30+00:00
Summary:     Set up base ARRAY to be compatible with postgresql.ARRAY.

For some reason, when ARRAY was added to the base it was never linked
to postgresql.ARRAY.   Link the two types and also make base
ARRAY the schema event target so that it supports the same
features as postgresql.ARRAY.

Change-Id: I82fa6c9d2b8c5028dba3a009715f7bc296b2bc0b
Fixes: #3964

Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/86c43d2e0f0c/
Changeset:   86c43d2e0f0c
Branch:      None
User:        zzzeek
Date:        2017-04-10 18:36:16+00:00
Summary:     Compare entities also on chop_path

When comparing query._current_path to options, the path chop
was not taking into account that the query or the options are
against aliased classes that don't match the mapper.

The issue does not seem to take place for the Load() version
of _chop_path.

Fixed bug to improve upon the specificity of loader options that
take effect subsequent to the lazy load of a related entity, so
that the loader options will match to an aliased or non-aliased
entity more specifically if those options include entity information.

Fixes: #3963
Change-Id: Ifdff37d579042fcc62bdeabce9e2413e9a03fbba

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5b81dbcfa388/
Changeset:   5b81dbcfa388
Branch:      master
User:        zzzeek
Date:        2017-04-10 18:59:14+00:00
Summary:     Merge "Compare entities also on chop_path"
Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Add new "expanding" feature to bindparam()

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/7d9f241d63b7/
Changeset:   7d9f241d63b7
Branch:      master
User:        zzzeek
Date:        2017-04-07 19:53:49+00:00
Summary:     Add new "expanding" feature to bindparam()

Added a new kind of :func:`.bindparam` called "expanding".  This is
for use in ``IN`` expressions where the list of elements is rendered
into individual bound parameters at statement execution time, rather
than at statement compilation time.  This allows both a single bound
parameter name to be linked to an IN expression of multiple elements,
as well as allows query caching to be used with IN expressions.  The
new feature allows the related features of "select in" loading and
"polymorphic in" loading to make use of the baked query extension
to reduce call overhead.   This feature should be considered to be
**experimental** for 1.2.

Fixes: #3953
Change-Id: Ie708414a3ab9c0af29998a2c7f239ff7633b1f6e

Affected #:  12 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Consider mysql partition options separately from other table options

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f1ffcc717fdf/
Changeset:   f1ffcc717fdf
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-06 16:35:34+00:00
Summary:     Consider mysql partition options separately from other table options

Move down all the PARTITION, SUBPARTITION options
into a separate segment so that they come out at the
end of CREATE TABLE after the table options.

Change-Id: Iaa1c823848c93680ca22d72bda1b7c49742b9060
Fixes: #3961
(cherry picked from commit 93b11905e599a6d73a85d2085e15385ebf46cdc6)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Consider mysql partition options separately from other table options

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/93b11905e599/
Changeset:   93b11905e599
Branch:      master
User:        zzzeek
Date:        2017-04-06 16:12:26+00:00
Summary:     Consider mysql partition options separately from other table options

Move down all the PARTITION, SUBPARTITION options
into a separate segment so that they come out at the
end of CREATE TABLE after the table options.

Change-Id: Iaa1c823848c93680ca22d72bda1b7c49742b9060
Fixes: #3961

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/da28e8f72313/
Changeset:   da28e8f72313
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-06 13:54:48+00:00
Summary:     - 1.1.10 prep

Change-Id: Ieec7379402ce35d3d0c15a5e6b5056e9d83071cf

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/764126039cd2/
Changeset:   764126039cd2
Branch:      master
User:        zzzeek
Date:        2017-04-06 13:55:04+00:00
Summary:     - add placeholder for 1.1.10

Change-Id: I068dd3b47dec200740db617891a64798db8f1734

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Support Postgresql INTERVAL fields spec/reflection

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b39b6023c57b/
Changeset:   b39b6023c57b
Branch:      master
User:        zzzeek
Date:        2017-04-05 17:55:10+00:00
Summary:     Support Postgresql INTERVAL fields spec/reflection

Added support for all possible "fields" identifiers when reflecting the
Postgresql ``INTERVAL`` datatype, e.g. "YEAR", "MONTH", "DAY TO
MINUTE", etc..   In addition, the :class:`.postgresql.INTERVAL`
datatype itself now includes a new parameter
:paramref:`.postgresql.INTERVAL.fields` where these qualifiers can be
specified; the qualifier is also reflected back into the resulting
datatype upon reflection / inspection.

Change-Id: I33816e68c533b023e0632db6f4e73fefd2de4721
Fixes: #3959

Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/86ef507cc73e/
Changeset:   86ef507cc73e
Branch:      None
User:        zzzeek
Date:        2017-04-05 16:18:36+00:00
Summary:     Double percent signs based on paramstyle, not dialect

This patch moves the "doubling" of percent signs into
the base compiler and makes it completely a product
of whether or not the paramstyle is format/pyformat or
not.   Without this paramstyle, percent signs
are not doubled across text(), literal_column(), and
column().

Change-Id: Ie2f278ab1dbb94b5078f85c0096d74dbfa049197
Fixes: #3740

Affected #:  10 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/06a90199c56b/
Changeset:   06a90199c56b
Branch:      master
User:        zzzeek
Date:        2017-04-05 17:06:00+00:00
Summary:     Merge "Double percent signs based on paramstyle, not dialect"
Affected #:  10 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9f82afea2595/
Changeset:   9f82afea2595
Branch:      None
User:        zzzeek
Date:        2017-04-04 17:45:06+00:00
Summary:     Recognize brackets, quoted_name in SQL Server schema

The SQL Server dialect now allows for a database and/or owner name
with a dot inside of it, using brackets explicitly in the string around
the owner and optionally the database name as well.  In addition,
sending the :class:`.quoted_name` construct for the schema name will
not split on the dot and will deliver the full string as the "owner".
:class:`.quoted_name` is also now available from the ``sqlalchemy.sql``
import space.

Change-Id: I77491d63ce47638bd23787d903ccde2f35a9d43d
Fixes: #2626

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1e7b730ce838/
Changeset:   1e7b730ce838
Branch:      master
User:        zzzeek
Date:        2017-04-04 18:28:39+00:00
Summary:     Merge "Recognize brackets, quoted_name in SQL Server schema"
Affected #:  7 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e48a9e78beff/
Changeset:   e48a9e78beff
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-04 18:03:01+00:00
Summary:     - 1.1.9

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/87b1404eda0f/
Changeset:   87b1404eda0f
Branch:      master
User:        zzzeek
Date:        2017-04-04 18:11:05+00:00
Summary:     - 1.1.9 release date

Change-Id: I8d1d55bde6424e4013c5b16bb27d6fc15fa225c2

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/10a3004f2ca2/
Changeset:   10a3004f2ca2
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-04 17:09:55+00:00
Summary:     Add much more detail to the "unhashable types" change

Change-Id: I34cbf54913b81ef2ae8b2e60f03feb78601460e5
Fixes: 3958

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0a44f97cb80f/
Changeset:   0a44f97cb80f
Branch:      master
User:        zzzeek
Date:        2017-04-04 17:10:29+00:00
Summary:     Add much more detail to the "unhashable types" change

Change-Id: I34cbf54913b81ef2ae8b2e60f03feb78601460e5
Fixes: 3958
(cherry picked from commit 10a3004f2ca29921c844f58689a5f02ed5f10e03)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4a4b17e0d3a1/
Changeset:   4a4b17e0d3a1
Branch:      None
User:        zzzeek
Date:        2017-04-04 14:02:39+00:00
Summary:     Apply SQL compilation to sqltext for column-level CHECK constraint

Fixed bug where a column-level :class:`.CheckConstraint` would fail
to compile the SQL expression using the underlying dialect compiler
as well as apply proper flags to generate literal values as
inline, in the case that the sqltext is a Core expression and
not just a plain string.   This was long-ago fixed for table-level
check constraints in 0.9 as part of :ticket:`2742`, which more commonly
feature Core SQL expressions as opposed to plain string expressions.

Change-Id: I1301ba4b40063e91bc47726aecc5f4990ffcaeda
Fixes: #3957

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b4686a0f7864/
Changeset:   b4686a0f7864
Branch:      master
User:        zzzeek
Date:        2017-04-04 14:22:32+00:00
Summary:     Merge "Apply SQL compilation to sqltext for column-level CHECK constraint"
Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 4 new changesets

[Bitbucket <com...@bi...>]

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d13734add349/
Changeset:   d13734add349
Branch:      None
User:        zzzeek
Date:        2017-04-04 13:06:13+00:00
Summary:     Ensure we check that SQL expression has an .info attribute

Fixed regression released in 1.1.8 due to :ticket:`3950` where the
deeper search for information about column types in the case of a
"schema type" or a :class:`.TypeDecorator` would produce an attribute
error if the mapping also contained a :obj:`.column_property`.

Change-Id: I38254834d3d79c9b339289a8163eb4789ec4c931
Fixes: #3956

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1ad5ad165d35/
Changeset:   1ad5ad165d35
Branch:      None
User:        zzzeek
Date:        2017-04-04 13:07:14+00:00
Summary:     Ensure we check that SQL expression has an .info attribute

Fixed regression released in 1.1.8 due to :ticket:`3950` where the
deeper search for information about column types in the case of a
"schema type" or a :class:`.TypeDecorator` would produce an attribute
error if the mapping also contained a :obj:`.column_property`.

Change-Id: I38254834d3d79c9b339289a8163eb4789ec4c931
Fixes: #3956
(cherry picked from commit d13734add349ec6763cce8b194806c5afe988000)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e28c3c7ec0d7/
Changeset:   e28c3c7ec0d7
Branch:      master
User:        zzzeek
Date:        2017-04-04 14:08:49+00:00
Summary:     Merge "Ensure we check that SQL expression has an .info attribute"
Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/02023ac46ed3/
Changeset:   02023ac46ed3
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-04 14:09:01+00:00
Summary:     Merge "Ensure we check that SQL expression has an .info attribute" into rel_1_1
Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6524838950dc/
Changeset:   6524838950dc
Branch:      master
User:        Bertrand Janin
Date:        2017-04-04 13:11:25+00:00
Summary:     Fix typo.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/803a52436f2e/
Changeset:   803a52436f2e
Branch:      rel_1_1
User:        Bertrand Janin
Date:        2017-04-04 14:04:20+00:00
Summary:     Fix typo.

(cherry picked from commit 6524838950dca5721a7f7e9db3118d9245c64659)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/760e0d2e0891/
Changeset:   760e0d2e0891
Branch:      rel_1_0
User:        Bertrand Janin
Date:        2017-04-04 14:04:24+00:00
Summary:     Fix typo.

(cherry picked from commit 6524838950dca5721a7f7e9db3118d9245c64659)

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: ResultProxy won't autoclose connection until state flag is set

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9609f5ffb52c/
Changeset:   9609f5ffb52c
Branch:      master
User:        zzzeek
Date:        2017-04-04 01:13:08+00:00
Summary:     ResultProxy won't autoclose connection until state flag is set

Changed the mechanics of :class:`.ResultProxy` to unconditionally
delay the "autoclose" step until the :class:`.Connection` is done
with the object; in the case where Postgresql ON CONFLICT with
RETURNING returns no rows, autoclose was occurring in this previously
non-existent use case, causing the usual autocommit behavior that
occurs unconditionally upon INSERT/UPDATE/DELETE to fail.

Change-Id: I235a25daf4381b31f523331f810ea04450349722
Fixes: #3955
(cherry picked from commit 8ee363e4917b0dcd64a83b6d26e465c9e61e0ea5)
(cherry picked from commit f52fb5282a046d26b6ee2778e03b995eb117c2ee)

Affected #:  6 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: ResultProxy won't autoclose connection until state flag is set

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f52fb5282a04/
Changeset:   f52fb5282a04
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-04 01:12:39+00:00
Summary:     ResultProxy won't autoclose connection until state flag is set

Changed the mechanics of :class:`.ResultProxy` to unconditionally
delay the "autoclose" step until the :class:`.Connection` is done
with the object; in the case where Postgresql ON CONFLICT with
RETURNING returns no rows, autoclose was occurring in this previously
non-existent use case, causing the usual autocommit behavior that
occurs unconditionally upon INSERT/UPDATE/DELETE to fail.

Change-Id: I235a25daf4381b31f523331f810ea04450349722
Fixes: #3955
(cherry picked from commit 8ee363e4917b0dcd64a83b6d26e465c9e61e0ea5)

Affected #:  6 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d2c733742f28/
Changeset:   d2c733742f28
Branch:      master
User:        zzzeek
Date:        2017-04-03 21:31:18+00:00
Summary:     - fix version identifier

Change-Id: I63abfb167f54ea2ea2f8bf4ba22ab38b60c5d59c

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2281ac7f1c64/
Changeset:   2281ac7f1c64
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-03 21:31:30+00:00
Summary:     - fix version identifier

Change-Id: If3bad7b79a61be6e421883727a430bdc5d9745db

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/7bb4923391f9/
Changeset:   7bb4923391f9
Branch:      None
User:        zzzeek
Date:        2017-04-03 16:14:33+00:00
Summary:     Use consistent method signature for Alias.self_group()

Fixed bug where the use of an :class:`.Alias` object in a column
context would raise an argument error when it tried to group itself
into a parenthesized expression.   Using :class:`.Alias` in this way
is not yet a fully supported API, however it applies to some end-user
recipes and may have a more prominent role in support of some
future Postgresql features.

Change-Id: I81717e30416e0350f08d1e022c3d84656e0a9735
Fixes: #3939

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6dfc5b36b869/
Changeset:   6dfc5b36b869
Branch:      master
User:        zzzeek
Date:        2017-04-03 16:37:35+00:00
Summary:     Merge "Use consistent method signature for Alias.self_group()"
Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6d7d48af0dec/
Changeset:   6d7d48af0dec
Branch:      master
User:        zzzeek
Date:        2017-04-01 17:47:42+00:00
Summary:     Return self when Variant.coerce_compared_value would return impl

Fixed regression released in 1.1.5 due to :ticket:`3859` where
adjustments to the "right-hand-side" evaluation of an expression
based on :class:`.Variant` to honor the underlying type's
"right-hand-side" rules caused the :class:`.Variant` type
to be inappropriately lost, in those cases when we *do* want the
left-hand side type to be transferred directly to the right hand side
so that bind-level rules can be applied to the expression's argument.

Change-Id: Ia54dbbb19398549d654b74668753c4152599d900
Fixes: #3952

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6896d2bb4753/
Changeset:   6896d2bb4753
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-01 17:48:25+00:00
Summary:     Return self when Variant.coerce_compared_value would return impl

Fixed regression released in 1.1.5 due to :ticket:`3859` where
adjustments to the "right-hand-side" evaluation of an expression
based on :class:`.Variant` to honor the underlying type's
"right-hand-side" rules caused the :class:`.Variant` type
to be inappropriately lost, in those cases when we *do* want the
left-hand side type to be transferred directly to the right hand side
so that bind-level rules can be applied to the expression's argument.

Change-Id: Ia54dbbb19398549d654b74668753c4152599d900
Fixes: #3952
(cherry picked from commit 6d7d48af0dec6325f87ce497f769827107ad5035)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b32a0fd286de/
Changeset:   b32a0fd286de
Branch:      master
User:        zzzeek
Date:        2017-04-01 15:36:52+00:00
Summary:     - 1.1.9 placeholder

Change-Id: Ic7897b5e05d7a20b280d4412d3bdf2ebc85905d4

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0d1383fc1ba1/
Changeset:   0d1383fc1ba1
Branch:      rel_1_1
User:        zzzeek
Date:        2017-04-01 15:37:13+00:00
Summary:     - 1.1.9 prep

Change-Id: I89f403529969f703f3b153fda317f163137686db

Affected #:  2 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f7ea0149fc0e/
Changeset:   f7ea0149fc0e
Branch:      rel_1_1
User:        zzzeek
Date:        2017-03-31 18:24:06+00:00
Summary:     - 1.1.8

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1daacdb408e0/
Changeset:   1daacdb408e0
Branch:      master
User:        zzzeek
Date:        2017-03-31 18:31:13+00:00
Summary:     - 1.1.8 release date

Change-Id: I6243e620e55ad862e8494d64cc754badce25097d

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/07b63894cb8f/
Changeset:   07b63894cb8f
Branch:      master
User:        zzzeek
Date:        2017-03-30 21:52:10+00:00
Summary:     Track SchemaEventTarget types in as_mutable()

Fixed bug in :mod:`sqlalchemy.ext.mutable` where the
:meth:`.Mutable.as_mutable` method would not track a type that had
been copied using :meth:`.TypeEngine.copy`.  This became more of
a regression in 1.1 compared to 1.0 because the :class:`.TypeDecorator`
class is now a subclass of :class:`.SchemaEventTarget`, which among
other things indicates to the parent :class:`.Column` that the type
should be copied when the :class:`.Column` is.  These copies are
common when using declarative with mixins or abstract classes.

Change-Id: Ib04df862c58263185dbae686c548fea3e12c46f1
Fixes: #3950

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/502a46b64e04/
Changeset:   502a46b64e04
Branch:      rel_1_1
User:        zzzeek
Date:        2017-03-30 21:52:56+00:00
Summary:     Track SchemaEventTarget types in as_mutable()

Fixed bug in :mod:`sqlalchemy.ext.mutable` where the
:meth:`.Mutable.as_mutable` method would not track a type that had
been copied using :meth:`.TypeEngine.copy`.  This became more of
a regression in 1.1 compared to 1.0 because the :class:`.TypeDecorator`
class is now a subclass of :class:`.SchemaEventTarget`, which among
other things indicates to the parent :class:`.Column` that the type
should be copied when the :class:`.Column` is.  These copies are
common when using declarative with mixins or abstract classes.

Change-Id: Ib04df862c58263185dbae686c548fea3e12c46f1
Fixes: #3950
(cherry picked from commit 07b63894cb8ff9529b406f196b5d7cb9af209e9e)

Affected #:  3 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.