delta/python-packages/sqlalchemy.git/doc, branch pr/310

Minor grammatical improvements in doc/build/intro.rst.

2016-10-05T19:07:57+00:00

Check for __clause_element__() in ORM insert/update

2016-10-05T16:11:53+00:00

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

Check row for None with implicit returning PK to accommodate ON CONFLICT

2016-10-04T21:31:40+00:00

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

Merge "Enhance "raise" strategy to include "raise_on_sql" option"

2016-10-04T20:48:08+00:00

Merge "Honor additional row coming in with value of None"

2016-10-04T18:41:43+00:00

- add a few more changes and try to break some out into

2016-10-04T16:33:37+00:00

ORM behavioral changes

Change-Id: I633ff10907b60111d3d0de0970fd384be7931d00

Enhance "raise" strategy to include "raise_on_sql" option

2016-10-04T16:09:29+00:00

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

Honor additional row coming in with value of None

2016-10-04T16:07:08+00:00

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

- add a note to baked documentation indicating it is not

2016-10-04T16:01:12+00:00

really of general use.  This extension is there only
for those who really want it based on observed performance
characteristics.

Change-Id: I2f612f26fdef4ddbeb1158ab1b344fad7083b11c

Use schema_name() for SQL Server default schema

2016-10-04T15:32:20+00:00

Changed the query used to get "default schema name", from one that
queries the database principals table to using the
"schema_name()" function, as issues have been reported that the
former system was unavailable on the Azure Data Warehouse edition.
It is hoped that this will finally work across all SQL Server
versions and authentication styles.

Change-Id: Ic11bd4162c0d6a60432ae44876e86512703c1f81
Fixes: #3810