| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
- replace misleading mysql-compatibility chart with newer verbiage from 0.7, 0.8 etc.
|
| | |
|
| | |
|
| |
|
|
| |
such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
in 0.7.4, which ensures that the connection
is in a valid state before attempting to call
rollback()/prepare()/release() on savepoint
and two-phase transactions.
|
| | |
|
| |
|
|
| |
support inline formatting in docutils 0.8
|
| | |
|
| |
|
|
|
| |
a tuple is inadvertently passed to session.query()
[ticket:2297].
|
| |
|
|
|
| |
object in a boolean context within query.get()
[ticket:2310].
|
| |
|
|
| |
works. [ticket:1776]
|
| |
|
|
|
|
| |
same modified index behavior in PG 9 affected
primary key reflection on a renamed column.
[ticket:2291].
|
| |
|
|
|
|
| |
after CHARSET, which appears to be part of
MySQL's arbitrary rules regarding if it will actually
work or not. [ticket:2225]
|
| |
|
|
|
| |
be ignored in the "inner" query within a
subquery eager load. [ticket:2287].
|
| | |
|
| | |
|
| |
|
|
| |
[ticket:2272]
|
| |
|
|
|
|
|
| |
Select would fail if a selectable were passed.
[ticket:2270]. However, the FROM behavior is
still incorrect here, so you need 0.7 in
any case for this use case to be usable.
|
| |
|
|
|
|
|
|
|
| |
used internally to resolve import cycles,
such that the usage of __import__ is completed
when the import of sqlalchemy or sqlalchemy.orm
is done, thereby avoiding any usage of __import__
after the application starts new threads,
fixes [ticket:2279].
|
| | |
|
| | |
|
| |
|
|
| |
- ensure mapper has "None" default for get_bind()
|
| |
|
|
|
|
|
| |
from a joined-inh structure to itself on
relationship() with join condition on the child
table would convert the lead entity into the
joined one inappropriately. [ticket:2234]
|
| |
|
|
| |
applies to 0.7
|
| | |
|
| |
|
|
| |
[ticket:2212]
|
| |
|
|
|
| |
quote symbol "'" for XA commands instead
of '"'. [ticket:2186].
|
| |
|
|
|
|
|
| |
sorting of persistent + pending objects during
flush would produce an illegal comparison,
if the persistent object primary key
is not a single integer. [ticket:2228]
|
| | |
|
| |
|
|
|
|
|
|
|
| |
ForeignKeyConstraint refers to a column name in
the parent that is not found.
- add tests for [ticket:2226], as if we hit each @declared_attr
directly with obj.__get__(obj, name) instead of using
getattr(cls, name). Basic inheritance mechanics are improperly
used in this case, so 2226 is invalid.
|
| |
|
|
| |
joinedload() is mentioned
|
| |
|
|
|
|
| |
used by query.join() would be inconsistent
if against a column expression that combined
multiple entities together. [ticket:2197]
|
| |
|
|
|
|
|
|
| |
generate the correct DDL. [ticket:2220]
- Fixed bug whereby "warn on unicode" flag
would get set for the String type
when used with certain dialects. This
bug is not in 0.7.
|
| |
|
|
|
|
|
|
|
| |
redefined __hash__() or __eq__() to something
non-standard, which is a supported use case
as SQLA should never consult these,
the methods would be consulted if the class
was part of a "composite" (i.e. non-single-entity)
result set. [ticket:2215]
|
| |
|
|
|
|
|
| |
as well as when using a "dynamic" relationship
against a parent will generate unique
bindparams, rather than incorrectly repeating
the same bindparam. [ticket:2207].
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- rewrite "getting a session" docs to delineate
all sessionmaker() use cases distinctly
- rewrite "Managing Transactions" doc to spell out
each specific step completely, [ticket:2204]
- add to create_engine() and main "engine" doc
an unambiguous statement that the create_engine()
does not create a connection
- other link fixes
- rewrite "deleting" section so that "deleting from collections"
is separate, well-described, [ticket:2202]
- rephrase "autocommit mode" into its own section, move it down,
put some bold text that you shouldn't be using it.
- simplify the "subtransactions" section and make it local to
"autocommit" since it is utterly unneeded by anybody.
- oracle is not doing 2-phase anytime soon
|
| |
|
|
|
|
| |
up if: column_property() against subquery +
joinedload + LIMIT + order by the column
property() occurred. [ticket:2188].
|
| |
|
|
|
| |
correspondence in a selectable with the
same column repeated. Affects [ticket:2188].
|
| |
|
|
|
| |
used the wrong form, example for cascade_backref used the wrong names.
- rewrite relationship cascade_backrefs doc
|
| | |
|
| |
|
|
|
| |
cx_oracle _Error.code to get at the code,
[ticket:2200].
|
| |
|
|
|
|
|
| |
assertion in Query which would attempt
to raise if a generative method were called
after from_statement() were called.
[ticket:2199].
|
| |
|
|
|
|
| |
the "adapt" step when used in result sets or
bound parameters. This issue is not in 0.7.
[ticket:2159]
|
| |
|
|
|
|
| |
collection wouldn't be cleared of expunged
states, raising an error if they later
became transient [ticket:2182].
|
| |
|
|
|
|
|
|
|
| |
a RowProxy result row such that no exception
throw is generated internally;
NoSuchColumnError() also will generate its
message regardless of whether or not the column
construct can be coerced to a string.
[ticket:2178].
|
| |
|
|
|
|
|
| |
MATCH operator. A potential floating-point
inaccuracy issue was fixed, and certain tests
of the MATCH operator only execute within an
EN-oriented locale for now. [ticket:2175].
|
| |
|
|
|
|
|
| |
when the "identity" key isn't detected on
flush, to include the common cause that
the Column isn't set up to detect
auto-increment correctly; [ticket:2170].
|