sqlalchemy-commits

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3a6b75870bdc/
Changeset:   3a6b75870bdc
Branch:      None
User:        zzzeek
Date:        2017-03-06 21:50:13+00:00
Summary:     - update asktom link, fixes #3925

Change-Id: Ibd63311dfccebbdf67e8ad7dc56ad311bf573895

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d22029bfc667/
Changeset:   d22029bfc667
Branch:      rel_1_0
User:        zzzeek
Date:        2017-03-06 21:50:51+00:00
Summary:     - update asktom link, fixes #3925

Change-Id: Ibd63311dfccebbdf67e8ad7dc56ad311bf573895
(cherry picked from commit 3a6b75870bdc7aa8fe70296cc3fc94ea06f16417)

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/f4c4f784cde8/
Changeset:   f4c4f784cde8
Branch:      None
User:        zzzeek
Date:        2017-03-06 22:20:06+00:00
Summary:     Don't cache savepoint identifiers

Fixed bug in compiler where the string identifier of a savepoint would
be cached in the identifier quoting dictionary; as these identifiers
are arbitrary, a small memory leak could occur if a single
:class:`.Connection` had an unbounded number of savepoints used,
as well as if the savepoint clause constructs were used directly
with an unbounded umber of savepoint names.   The memory leak does
**not** impact the vast majority of cases as normally the
:class:`.Connection`, which renders savepoint names with a simple
counter starting at "1", is used on a per-transaction or
per-fixed-number-of-transactions basis before being discarded.

The savepoint name in virtually all cases does not require quoting
at all, however to support potential third party use cases
the "check for quotes needed" logic is retained, at a small
performance cost.   Uncondtionally quoting the name is another
option, but this would turn the name into a case sensitive name
which runs the risk of poor interactions with existing deployments
that may be looking at these names in other contexts.

Change-Id: I6b53c96abf7fdf1840592bbca5da81347911844c
Fixes: #3931

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b54cefc379dc/
Changeset:   b54cefc379dc
Branch:      master
User:        zzzeek
Date:        2017-03-07 00:12:40+00:00
Summary:     Merge "Don't cache savepoint identifiers"
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/74bec18c2a3c/
Changeset:   74bec18c2a3c
Branch:      None
User:        zzzeek
Date:        2017-03-07 19:54:53+00:00
Summary:     - document ForeignKeyConstraint columns / elements, fixes #2904

Change-Id: Ia50a3100d1bd88020c30224932b16aeadd7f4c75

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/69db95b3a8ca/
Changeset:   69db95b3a8ca
Branch:      rel_1_0
User:        zzzeek
Date:        2017-03-07 19:55:25+00:00
Summary:     - document ForeignKeyConstraint columns / elements, fixes #2904

Change-Id: Ia50a3100d1bd88020c30224932b16aeadd7f4c75
(cherry picked from commit 74bec18c2a3cc8e9c031808fc44bc0f2c5af8b43)

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/86cf3eb71c3c/
Changeset:   86cf3eb71c3c
Branch:      None
User:        zzzeek
Date:        2017-03-14 20:58:17+00:00
Summary:     Improve serializer behavior

Fix an issue where the Annotated system needs to have a
__reduce__ method, also see why we can't default to HIGHEST_PROTOCOL.
This latter part might not be a good idea until 1.2 for compatibility
reasons.

Change-Id: I0239e38259fc768c9e3b6c448c29161e271a969c
Fixes: #3918

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/18b2dea9a48a/
Changeset:   18b2dea9a48a
Branch:      master
User:        zzzeek
Date:        2017-03-14 23:38:06+00:00
Summary:     Merge "Improve serializer behavior"
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/f3b6f4f8da52/
Changeset:   f3b6f4f8da52
Branch:      None
User:        zzzeek
Date:        2017-03-14 21:01:07+00:00
Summary:     Add "empty in" strategies; default to "static"

The longstanding behavior of the :meth:`.Operators.in_` and
:meth:`.Operators.not_in_` operators emitting a warning when
the right-hand condition is an empty sequence has been revised;
a new flag :paramref:`.create_engine.empty_in_strategy` allows an
empty "IN" expression to generate a simple boolean expression, or
to invoke the previous behavior of dis-equating the expression to
itself, with or without a warning.  The default behavior is now
to emit the simple boolean expression, allowing an empty IN to
be evaulated without any performance penalty.

Change-Id: I65cc37f2d7cf65a59bf217136c42fee446929352
Fixes: #3907

Affected #:  11 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0a35ccc6bd1a/
Changeset:   0a35ccc6bd1a
Branch:      master
User:        zzzeek
Date:        2017-03-14 23:39:37+00:00
Summary:     Merge "Add "empty in" strategies; default to "static""
Affected #:  11 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/b6a6ffa4c0e0/
Changeset:   b6a6ffa4c0e0
Branch:      None
User:        zzzeek
Date:        2017-03-14 23:41:21+00:00
Summary:     Consult _select_from_entity in _adjust_for_single_inheritance

Fixed bug in single-table inheritance where the select_from()
argument would not be taken into account when limiting rows
to a subclass.  Previously, only expressions in the
columns requested would be taken into account.

Change-Id: Id353c45eade52b264d8f6685a58ba53975669eea
Fixes: #3891

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b5b6e9574854/
Changeset:   b5b6e9574854
Branch:      master
User:        zzzeek
Date:        2017-03-15 21:12:03+00:00
Summary:     Merge "Consult _select_from_entity in _adjust_for_single_inheritance"
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/fadb8d61babb/
Changeset:   fadb8d61babb
Branch:      None
User:        RazerM
Date:        2017-03-17 18:02:15+00:00
Summary:     Implement comments for tables, columns

Added support for SQL comments on :class:`.Table` and :class:`.Column`
objects, via the new :paramref:`.Table.comment` and
:paramref:`.Column.comment` arguments.   The comments are included
as part of DDL on table creation, either inline or via an appropriate
ALTER statement, and are also reflected back within table reflection,
as well as via the :class:`.Inspector`.   Supported backends currently
include MySQL, Postgresql, and Oracle.

Co-authored-by: Mike Bayer <mi...@zz...>
Fixes: #1546
Change-Id: Ib90683850805a2b4ee198e420dc294f32f15d35d

Affected #:  19 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d96fc5d02a92/
Changeset:   d96fc5d02a92
Branch:      master
User:        zzzeek
Date:        2017-03-17 18:16:27+00:00
Summary:     Merge "Implement comments for tables, columns"
Affected #:  19 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/08f42a915a40/
Changeset:   08f42a915a40
Branch:      None
User:        zzzeek
Date:        2017-03-27 15:15:41+00:00
Summary:     Add safe_reraise() + warnings only to Connection._autorollback

Added an exception handler that will warn for the "cause" exception on
Py2K when the "autorollback" feature of :class:`.Connection` itself
raises an exception. In Py3K, the two exceptions are naturally reported
by the interpreter as one occurring during the handling of the other.
This is continuing with the series of changes for rollback failure
handling that were last visited as part of :ticket:`2696` in 1.0.12.

Change-Id: I600ba455a14ebaea27c6189889181f97c632f179
Fixes: #3946
(cherry picked from commit c0a224aba3d4e2a41f92a29f9d18c6cb9d09d61f)

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c531deda1042/
Changeset:   c531deda1042
Branch:      rel_1_1
User:        zzzeek
Date:        2017-03-27 15:34:55+00:00
Summary:     Merge "Add safe_reraise() + warnings only to Connection._autorollback" into rel_1_1
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/c0a224aba3d4/
Changeset:   c0a224aba3d4
Branch:      None
User:        zzzeek
Date:        2017-03-27 15:14:24+00:00
Summary:     Add safe_reraise() + warnings only to Connection._autorollback

Added an exception handler that will warn for the "cause" exception on
Py2K when the "autorollback" feature of :class:`.Connection` itself
raises an exception. In Py3K, the two exceptions are naturally reported
by the interpreter as one occurring during the handling of the other.
This is continuing with the series of changes for rollback failure
handling that were last visited as part of :ticket:`2696` in 1.0.12.

Change-Id: I600ba455a14ebaea27c6189889181f97c632f179
Fixes: #3946

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6eae79ac55ea/
Changeset:   6eae79ac55ea
Branch:      master
User:        zzzeek
Date:        2017-03-27 16:27:56+00:00
Summary:     Merge "Add safe_reraise() + warnings only to Connection._autorollback"
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/dca69f3f1eeb/
Changeset:   dca69f3f1eeb
Branch:      rel_1_1
User:        zzzeek
Date:        2017-03-27 21:25:25+00:00
Summary:     - 1.1.7

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f3c368357c21/
Changeset:   f3c368357c21
Branch:      master
User:        zzzeek
Date:        2017-03-27 21:34:15+00:00
Summary:     - update release date for 1.1.7

Change-Id: I6ce86e2e0c54135194c60d99b433b2f38c467dbd

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/9aebc08f82bf/
Changeset:   9aebc08f82bf
Branch:      rel_1_1
User:        zzzeek
Date:        2017-03-29 20:15:39+00:00
Summary:     - 1.1.8 prep

Change-Id: I36f2f2be3ce49931bb9fc304b5abfd67824290cb

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6220e09f6149/
Changeset:   6220e09f6149
Branch:      master
User:        zzzeek
Date:        2017-03-29 20:15:53+00:00
Summary:     - start changelog for 1.1.8

Change-Id: I6c23f43ca76aeca469980fc8be228af20c2c700d

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/e851bf436b34/
Changeset:   e851bf436b34
Branch:      rel_1_1
User:        Ihor Kalnytskyi
Date:        2017-03-30 14:16:35+00:00
Summary:     Docs/faq/performance

Some updates for FAQ/Performance documentation page:

* Fix typo in testing script.
* Populate testing script with one more way to achieve higher performance.

See commit messages for details.

Change-Id: Id6fbf328164b14b3b58ca9616b103a35e72f7b8f
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/345
(cherry picked from commit a4c17c1397c68d109bcf0603644f3200ab2e82f5)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/707768ec5d29/
Changeset:   707768ec5d29
Branch:      rel_1_0
User:        Ihor Kalnytskyi
Date:        2017-03-30 14:16:42+00:00
Summary:     Docs/faq/performance

Some updates for FAQ/Performance documentation page:

* Fix typo in testing script.
* Populate testing script with one more way to achieve higher performance.

See commit messages for details.

Change-Id: Id6fbf328164b14b3b58ca9616b103a35e72f7b8f
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/345
(cherry picked from commit a4c17c1397c68d109bcf0603644f3200ab2e82f5)

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.

[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/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/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/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/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/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: 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/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/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/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/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: 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.