sqlalchemy-commits — SVN commits logged to this list

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - open for 1.1.3

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/39ac19510989/
Changeset:   39ac19510989
Branch:      None
User:        zzzeek
Date:        2016-10-20 15:46:41+00:00
Summary:     - open for 1.1.3

Change-Id: I283e52a7a63ec4f7a285aba1b41627f11b7ad41b

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: kaiyou: Remove some legacy dead code from the declared_attr logic

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/cc74f434fdeb/
Changeset:   cc74f434fdeb
Branch:      rel_1_0
User:        kaiyou
Date:        2016-10-16 14:55:22+00:00
Summary:     Remove some legacy dead code from the declared_attr logic

The second 'if' condition was never called because the original
condition always returns.

(cherry picked from commit d18221c542bf4d7381be2afdcd4c098698ff8eae)

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: Rewrite migration notes for [ticket:3514]

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/76ec285ba452/
Changeset:   76ec285ba452
Branch:      None
User:        zzzeek
Date:        2016-10-19 17:09:16+00:00
Summary:     Rewrite migration notes for [ticket:3514]

The change to "evaluates none" datatypes in the ORM was
not fully described in the migration notes, missing the
key behavioral change that a column which is missing a default
entirely will not receive a value for a missing JSON column now.
The issue here touched upon a revisit of the assumptions
in [ticket:3514], but overall the old behavior "worked" mostly
because the ORM wants to explicitly render NULL into an INSERT
for column values that are missing, which itself is a legacy
behavior which should be considered for possible removal in
a future major release.  Given that "missing ORM value + no
column default set up == dont put it in the INSERT" would be
the most intuitive behavior, the move in [ticket:3514] represents
a step in this direction.

Change-Id: I454d5bb0773bd73d9864925dcc47f1f0810e33ba
Fixes: #3830

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: - 1.1.2

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2ee5d42e24d2/
Changeset:   2ee5d42e24d2
Branch:      None
User:        zzzeek
Date:        2016-10-17 18:29:01+00:00
Summary:     - 1.1.2

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: zzzeek: - correct ticket link markup

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/480b4e467c6f/
Changeset:   480b4e467c6f
Branch:      None
User:        zzzeek
Date:        2016-10-17 18:27:53+00:00
Summary:     - correct ticket link markup

Change-Id: I49df318c77f9f539541e7edea857bd256aca2844

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/f917b353e88a/
Changeset:   f917b353e88a
Branch:      None
User:        zzzeek
Date:        2016-10-17 16:14:41+00:00
Summary:     Add a qualifying character to multi INSERT..VALUES parameter names

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.

Change-Id: I3188d100fe4d322a47d344d6a63d3e40b915f228
Fixes: #3828

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7d8a6b2614da/
Changeset:   7d8a6b2614da
Branch:      None
User:        zzzeek
Date:        2016-10-17 16:49:12+00:00
Summary:     Merge "Add a qualifying character to multi INSERT..VALUES parameter names"
Affected #:  5 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: Remove the use of the word "fundamental" to describe ColumnElements

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f9432a0287c7/
Changeset:   f9432a0287c7
Branch:      None
User:        zzzeek
Date:        2016-10-17 16:35:26+00:00
Summary:     Remove the use of the word "fundamental" to describe ColumnElements

The context is unclear if "fundamental" refers to the object's
role within a SELECT composition or within the class hierarchy
of ClauseElement classes.

Change-Id: I10bbf324fc09034cc27398867b7eca6b6f127abe
Fixes: #3793

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: 6 new changesets

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

6 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/665b92d83f3a/
Changeset:   665b92d83f3a
Branch:      None
User:        zzzeek
Date:        2016-10-14 17:26:35+00:00
Summary:     Check for __module__ not present in util.wrap_callable()

The newly added wrap_callable() function assumes __module__
is present when this is not the case for objects such as
functools.partial.

Change-Id: Ia226260e9a65419e26d5c1f7187512f7fd4bb7c1
Fixes: #3823

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d18221c542bf/
Changeset:   d18221c542bf
Branch:      None
User:        kaiyou
Date:        2016-10-16 14:45:54+00:00
Summary:     Remove some legacy dead code from the declared_attr logic

The second 'if' condition was never called because the original
condition always returns.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/4684cfb50836/
Changeset:   4684cfb50836
Branch:      None
User:        zzzeek
Date:        2016-10-17 15:28:43+00:00
Summary:     Merge "Check for __module__ not present in util.wrap_callable()"
Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ae7d2837b3c5/
Changeset:   ae7d2837b3c5
Branch:      None
User:        zzzeek
Date:        2016-10-17 15:28:36+00:00
Summary:     Assemble "don't joinedload other side" rule using query._current_path

Discovered during testing for [ticket:3822], the rule added
for [ticket:1495] will fail if the source object has propagated
options set up, which add elements to query._current_path.

Fixes: #3824
Change-Id: I3d96c96fee5f9b247f739d2136d18681ac61f2fe

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c02675b407b8/
Changeset:   c02675b407b8
Branch:      None
User:        zzzeek
Date:        2016-10-17 15:29:23+00:00
Summary:     Memoize load_path in all cases, run quick populators for path change

Adds a new variant to the "isnew" state within entity loading
for isnew=False, but the load path is new.  This is to address
the use case of an entity appearing in multiple places in
the row in a more generalized way than the fixes in [ticket:3431],
[ticket:3811] in that loading.py will be able to tell the
populator that this row is not "isnew" but is a "new" path
for the entity.   For the moment, the new information is only
being applied to the use of "quick" populators so that
simple column loads can take place on top of a deferred loader
from elsewhere in the row.

As part of this change, state.load_path() will now always
be populated with the "path" that was in effect when this state
was originally loaded, which for multi-path loads of the
same entity is still non-deterministic.  Ideally there'd be some
kind of "here's all the paths that loaded this state and how"
type of data structure though it's not clear if that could be
done while maintaining performance.

Fixes: #3822
Change-Id: Ib915365353dfcca09e15c24001a8581113b97d5e

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/8ef4f6a53864/
Changeset:   8ef4f6a53864
Branch:      master
User:        zzzeek
Date:        2016-10-17 16:13:01+00:00
Summary:     Add explicit copy() to Enum

The Boolean and Enum types both place SchemaType second in the
inheritance hierarchy.  In the case of Enum, this works
out that the copy() method is called from the base TypeEngine
which fails to transfer _create_events.   The test suite
doesn't seem to work with the inhertance hierarchy set up like
this as the event listeners don't work out, the _on_metadata_create
and _on_table_create hooks cause the production of an adapted type
which then adds event listeners that cause deque changed while
iteration.  It's not clear why Enum /Boolean don't have this problem.
But in any case it seems like the class mechanics for these types
remains fragile and would benefit from yet another refactor someday.

Change-Id: Ib641a5d2321b00f58bbe98dd0c5e789374db32b2
Fixes: #3827

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/055b207a9f80/
Changeset:   055b207a9f80
Branch:      None
User:        Randy Barlow
Date:        2016-10-13 17:02:26+00:00
Summary:     Fix a minor grammatical error in the ORM tutorial.

Change-Id: I50daaee2645dd8aa2ee7217f4065589492ed0b7d

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/4a8522c70667/
Changeset:   4a8522c70667
Branch:      rel_1_0
User:        Randy Barlow
Date:        2016-10-13 17:04:41+00:00
Summary:     Fix a minor grammatical error in the ORM tutorial.

Change-Id: I50daaee2645dd8aa2ee7217f4065589492ed0b7d
(cherry picked from commit 055b207a9f80e1899a30cce8d11e79eb1136612a)

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: - setup for next version

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6b7b77896dd2/
Changeset:   6b7b77896dd2
Branch:      None
User:        zzzeek
Date:        2016-10-13 16:27:51+00:00
Summary:     - setup for next version

Change-Id: I4a7ef54bec3891821954061a9b4ed19d398989f3

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: mriedem: Update the Column.nullable docstring for the primary_key=True case

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a4a7880f37d9/
Changeset:   a4a7880f37d9
Branch:      rel_1_0
User:        mriedem
Date:        2016-10-10 16:28:54+00:00
Summary:     Update the Column.nullable docstring for the primary_key=True case

While reviewing a change that created a new table, the
primary_key column value was set to True but nullable was not
explicitly set, which led to some confusion over the default
behavior for the nullable column value when setting a primary_key.

Looking at the docs it's not clear, but the code shows that if
nullable is not specified, then nullable = not primary_key, so
nullable defaults to False when primary_key is True.

This patch adds a simple clarification to the docs so people
don't have to check the code.

Change-Id: I8553339d56fbae11370c7c6af6d8d4723163be1c
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/312
(cherry picked from commit 4b94ee113baab901aee881ad94851587c912f785)

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: mriedem: Update the Column.nullable docstring for the primary_key=True case

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4b94ee113baa/
Changeset:   4b94ee113baa
Branch:      master
User:        mriedem
Date:        2016-10-10 15:54:04+00:00
Summary:     Update the Column.nullable docstring for the primary_key=True case

While reviewing a change that created a new table, the
primary_key column value was set to True but nullable was not
explicitly set, which led to some confusion over the default
behavior for the nullable column value when setting a primary_key.

Looking at the docs it's not clear, but the code shows that if
nullable is not specified, then nullable = not primary_key, so
nullable defaults to False when primary_key is True.

This patch adds a simple clarification to the docs so people
don't have to check the code.

Change-Id: I8553339d56fbae11370c7c6af6d8d4723163be1c
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/312

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: 4 new changesets

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e47063bfe0de/
Changeset:   e47063bfe0de
Branch:      None
User:        scop
Date:        2016-10-08 17:42:50+00:00
Summary:     Spelling fixes

Affected #:  23 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/8c2c464cb8e1/
Changeset:   8c2c464cb8e1
Branch:      None
User:        scop
Date:        2016-10-08 17:42:50+00:00
Summary:     spelling: Postgresql -> PostgreSQL

Affected #:  60 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e5a063a87ce5/
Changeset:   e5a063a87ce5
Branch:      None
User:        scop
Date:        2016-10-08 17:42:50+00:00
Summary:     spelling: Postgis -> PostGIS

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b9d0e2d5c55f/
Changeset:   b9d0e2d5c55f
Branch:      None
User:        scop
Date:        2016-10-08 17:42:50+00:00
Summary:     spelling: Mysql -> MySQL

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: zzzeek: - 1.1.1

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/80861dffa9f2/
Changeset:   80861dffa9f2
Branch:      None
User:        zzzeek
Date:        2016-10-07 15:04:37+00:00
Summary:     - 1.1.1

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: zzzeek: Change autoincrement compileerror to a warning

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8a13957db790/
Changeset:   8a13957db790
Branch:      master
User:        zzzeek
Date:        2016-10-07 13:54:39+00:00
Summary:     Change autoincrement compileerror to a warning

Users are complaining that IntegrityError is no longer
raised.

Change-Id: I0855d5b7a98d4338f0910501b6e6d404ba33634d
Fixes: #3216

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/ae9300cac0ec/
Changeset:   ae9300cac0ec
Branch:      None
User:        zzzeek
Date:        2016-10-07 13:17:46+00:00
Summary:     Catch DBAPIError instead of ProgrammingError for pyodbc fail

Change-Id: Ide9e916d02fbbef549aa2838d1402c2b091e701d
Fixes: #3820

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/804ff38b37ec/
Changeset:   804ff38b37ec
Branch:      rel_1_0
User:        zzzeek
Date:        2016-10-07 13:18:17+00:00
Summary:     Catch DBAPIError instead of ProgrammingError for pyodbc fail

This is part of release 1.1.1 but the broken version
was unreleased in 1.0.16.

Change-Id: Ide9e916d02fbbef549aa2838d1402c2b091e701d
Fixes: #3820
(cherry picked from commit ae9300cac0ec398f92d9e523273403126a709134)

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: - set up for 1.1.1

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b1fe748feafd/
Changeset:   b1fe748feafd
Branch:      None
User:        zzzeek
Date:        2016-10-06 02:31:31+00:00
Summary:     - set up for 1.1.1

Change-Id: I569a03a6e86aa096be6744ecb479fe8485f7def6

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: zzzeek: - 1.1.0

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/56e199416f38/
Changeset:   56e199416f38
Branch:      None
User:        zzzeek
Date:        2016-10-05 20:59:00+00:00
Summary:     - 1.1.0

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/71030d67bd7c/
Changeset:   71030d67bd7c
Branch:      None
User:        zzzeek
Date:        2016-10-05 20:47:31+00:00
Summary:     Propagate execution_options at compile stage

Compiler can now set up execution options and additionally
will propagate autocommit from embedded CTEs.

Change-Id: I19db7b8fe4d84549ea95342e8d2040189fed1bbe
Fixes: #3805

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/fe9282034794/
Changeset:   fe9282034794
Branch:      master
User:        zzzeek
Date:        2016-10-05 20:52:15+00:00
Summary:     Merge "Propagate execution_options at compile stage"
Affected #:  5 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/df4639ab7172/
Changeset:   df4639ab7172
Branch:      None
User:        Randy Barlow
Date:        2016-10-05 19:07:57+00:00
Summary:     Minor grammatical improvements in doc/build/intro.rst.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/5e8b12e07b0f/
Changeset:   5e8b12e07b0f
Branch:      rel_1_0
User:        Randy Barlow
Date:        2016-10-05 20:43:46+00:00
Summary:     Minor grammatical improvements in doc/build/intro.rst.

(cherry picked from commit df4639ab717273490b17085d5cdb240eef3cf0c0)

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: Check for __clause_element__() in ORM insert/update

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/09b685b24b19/
Changeset:   09b685b24b19
Branch:      master
User:        zzzeek
Date:        2016-10-05 16:11:53+00:00
Summary:     Check for __clause_element__() in ORM insert/update

ORM attributes can now be assigned any object that is has a
``__clause_element__()`` attribute, which will result in inline
SQL the way any :class:`.ClauseElement` class does.  This covers other
mapped attributes not otherwise transformed by further expression
constructs.

As part of this, it was considered that we could add
__clause_element__() to ClauseElement, however this causes endless loops
in a "while" pattern and this pattern has been identified in third
party libraries.  Add a test to ensure we never make that change.

Change-Id: I9e15b3f1c4883fd3909acbf7dc81d034c6e3ce1d
Fixes: #3802

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: Check row for None with implicit returning PK to accommodate ON CONFLICT

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/20384e894577/
Changeset:   20384e894577
Branch:      master
User:        zzzeek
Date:        2016-10-04 21:31:40+00:00
Summary:     Check row for None with implicit returning PK to accommodate ON CONFLICT

An adjustment to ON CONFLICT such that the "inserted_primary_key"
logic is able to accommodate the case where there's no INSERT or
UPDATE and there's no net change.  The value comes out as None
in this case, rather than failing on an exception.

Change-Id: I0794e95c3ca262cb1ab2387167d96b8984225fce
Fixes: #3813

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/95d4cd304204/
Changeset:   95d4cd304204
Branch:      None
User:        zzzeek
Date:        2016-10-04 16:09:29+00:00
Summary:     Enhance "raise" strategy to include "raise_on_sql" option

The "raise_on_sql" option differentiates from "raise" in that
firing a lazy loader is OK as long as it does a simple
get from identity map.   Whereas "raise" is more useful
for the case that objects are to be detached.

As part of this, refactors the strategy initiation logic
a bit so that a LoaderStrategy itself knows what "key" was used
to create it, thus allowing variants of a single strategy
based on what the "lazy" argument is.  To achieve this we
have to also get rid of _get_strategy_by_cls().

Everything here is internal with the one exception of an apparently
undocumented, but not underscored, "strategy_class" key
on relationship().   Though it's not clear what
"strategy_class" accomplishes; at this point the strategy
system is extensible using Property.strategy_for().

Fixes: #3812
Change-Id: I812ad878ea5cf764e15f6f71cb39eee78a645d88

Affected #:  10 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e5a5a72e175d/
Changeset:   e5a5a72e175d
Branch:      master
User:        zzzeek
Date:        2016-10-04 20:48:08+00:00
Summary:     Merge "Enhance "raise" strategy to include "raise_on_sql" option"
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/c3abfe50645a/
Changeset:   c3abfe50645a
Branch:      None
User:        zzzeek
Date:        2016-10-04 16:07:08+00:00
Summary:     Honor additional row coming in with value of None

The change in #3431 still checks that the instance() is
non-None, deferring to other loading schemes if it is.
These columns are dedicated towards the entity however, so if the value
is None, we should set it.  If it conflicts, we are detecting that
in any case.

Change-Id: I223768e2898e843f953e910da1f9564b137d95e4
Fixes: #3811

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/aadbb5a1d1e0/
Changeset:   aadbb5a1d1e0
Branch:      master
User:        zzzeek
Date:        2016-10-04 18:41:43+00:00
Summary:     Merge "Honor additional row coming in with value of None"
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: - add a few more changes and try to break some out into

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ab8944b1bf41/
Changeset:   ab8944b1bf41
Branch:      None
User:        zzzeek
Date:        2016-10-04 16:33:37+00:00
Summary:     - add a few more changes and try to break some out into
ORM behavioral changes

Change-Id: I633ff10907b60111d3d0de0970fd384be7931d00

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.