1.1.0b3

Released: July 26, 2016

orm

[orm] [change] Removed a warning that dates back to 0.4 which emits when a same-named
relationship is placed on two mappers that inherits via joined or
single table inheritance. The warning does not apply to the
current unit of work implementation.
References: #3749

[sql] [bug] Fixed bug in new CTE feature for update/insert/delete stated
as a CTE inside of an enclosing statement (typically SELECT) whereby
oninsert and onupdate values weren't called upon for the embedded
statement.
References: #3745
[sql] [bug] Fixed bug in new CTE feature for update/insert/delete whereby
an anonymous (e.g. no name passed) CTE construct around
the statement would fail.
References: #3744

[postgresql] [bug] Fixed bug whereby TypeDecorator and Variant
types were not deeply inspected enough by the PostgreSQL dialect
to determine if SMALLSERIAL or BIGSERIAL needed to be rendered
rather than SERIAL.
This change is also backported to: 1.0.14
References: #3739

[oracle] [bug] Fixed bug in Select.with_for_update.of, where the Oracle
"rownum" approach to LIMIT/OFFSET would fail to accommodate for the
expressions inside the "OF" clause, which must be stated at the topmost
level referring to expression within the subquery. The expressions are
now added to the subquery if needed.
This change is also backported to: 1.0.14
References: #3741

[bug] [ext] Fixed bug in sqlalchemy.ext.baked where the unbaking of a
subquery eager loader query would fail due to a variable scoping
issue, when multiple subquery loaders were involved. Pull request
courtesy Mark Hahnenberg.
This change is also backported to: 1.0.15
References: #3743
[bug] [ext] sqlalchemy.ext.indexable will intercept IndexError as well
as KeyError when raising as AttributeError.
[ext] [feature] Added a "default" parameter to the new sqlalchemy.ext.indexable
extension.