delta/python-packages/sqlalchemy.git, branch no_auto_froms

Propose implicit FROM logic be limited to only those tables

2017-06-24T19:42:33+00:00

explicitly in the columns clause

A proposal to prevent "FROM A, B" styles of cartesian products
by simply disallowing from the FROM clause any table
that wasn't explicitly made part of the FROM clause
nor was selected from.

Change-Id: Ia8c3f5efa702a0cf9421fd8d899a808af51e0023

added link for CrateDB support

2017-06-23T19:16:18+00:00

Don't erase reflected comment in _init_existing

2017-06-20T13:48:49+00:00

Change-Id: Ie0b78c79367933486528ca0ba686d4a9f16922b1
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/370

Add ad-hoc mapped expressions

2017-06-19T21:41:39+00:00

Added a new feature :func:`.orm.with_expression` that allows an ad-hoc
SQL expression to be added to a specific entity in a query at result
time.  This is an alternative to the SQL expression being delivered as
a separate element in the result tuple.

Change-Id: Id8c479f7489fb02e09427837c59d1eabb2a6c014
Fixes: #3058

- 1.1.11 release date

2017-06-19T15:00:59+00:00

Change-Id: I351e5727368b67598d091e5153a66987e349f8f6

Merge "Handle SHOW VARIABLES returning no row"

2017-06-16T22:40:13+00:00

Merge "Add all versioning logic to _post_update()"

2017-06-16T20:41:14+00:00

Handle SHOW VARIABLES returning no row

2017-06-16T19:52:46+00:00

MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES"
command; the MySQL dialect will now handle when SHOW returns no
row, in particular for the initial fetch of SQL_MODE, and will
emit a warning that user permissions should be modified to allow the
row to be present.

Change-Id: I98e7a69230da397b17eae07b7e9d024fa7aeeb26
Fixes: #4007

Set complete FROM list for subquery eagerload's orig query

2017-06-16T17:02:31+00:00

Instead of checking that the "orig_entity" we receive applies
as a correct FROM element for the subquery we're building,
set the FROM clause of the query to exactly what it already
is based on column_descriptions (assuming there is no FROM
list already), thereby ensuring that the FROM list will remain
intact, regardless of what orig_entity turns out to be and
what the target_cols ultimately refer towards.

Fixed issue with subquery eagerloading which continues on from
the series of issues fixed in :ticket:`2699`, :ticket:`3106`,
:ticket:`3893` involving that the "subquery" contains the correct
FROM clause when beginning from a joined inheritance subclass
and then subquery eager loading onto a relationship from
the base class, while the query also includes criteria against
the subclass. The fix in the previous tickets did not accommodate
for additional subqueryload operations loading more deeply from
the first level, so the fix has been further generalized.

Change-Id: Ic909590814f71e577d8266b1dbc4c393dc48e019
Fixes: #4011

Repair WithinGroup.get_children()

2017-06-16T13:58:03+00:00

Fixed AttributeError which would occur in :class:`.WithinGroup`
construct during an iteration of the structure.

Change-Id: I563882d93c8c32292463a605b636aa60c77e9406
Fixes: #4012