| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
- use thread.join() for waiters_handled test
Conflicts:
test/engine/test_pool.py
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
"naming columns distinctly" and "column_prefix" sections since this is often what ppl are looking for. [ticket:2856] is related.
|
|
|
|
|
|
| |
query being generated would produce a "columns being replaced"
warning for a statement with two same-named columns,
as the internal SELECT wouldn't have use_labels set.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
when using the pypostgresql adapter, which returns these values
as lists vs. psycopg2's return type of string.
[ticket:2855]
Conflicts:
doc/build/changelog/changelog_09.rst
lib/sqlalchemy/__init__.py
|
| |
|
| |
|
|
|
|
|
| |
if the synonym and the table were in different remote schemas.
Patch to fix courtesy Kyle Derr. [ticket:2853]
|
|
|
|
| |
ipv6 addresses, e.g. surrounded by brackets. [ticket:2851]
|
|
|
|
|
|
|
|
| |
elements with a ``__clause_element__()`` method properly.
[ticket:2849]
Conflicts:
lib/sqlalchemy/sql/elements.py
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that the custom type isn't exposed to an operation that is against the
"impl" type's constraint, [ticket:2842]
- this change showed up as some recursion overflow in pickling with labels,
add a __reduce__() there....pickling of expressions is less and less something
that's very viable...
Conflicts:
lib/sqlalchemy/sql/elements.py
lib/sqlalchemy/sql/sqltypes.py
|
| |
|
|
|
|
|
| |
Conflicts:
doc/build/core/reflection.rst
|
| |
|
|
|
|
|
|
| |
server default for a column; this code was original from
PG system views which truncated the string for readability.
[ticket:2844]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of :class:`.ForeignKeyConstraint` is silently ignored on the MySQL
backend, will be reverted as of 0.9; this keyword will now render again, raising
errors on MySQL as it is not understood - the same behavior will also
apply to the ``initially`` keyword. In 0.8, the keywords will remain
ignored but a warning is emitted. Additionally, the ``match`` keyword
now raises a :class:`.CompileError` on 0.9 and emits a warning on 0.8;
this keyword is not only silently ignored by MySQL but also breaks
the ON UPDATE/ON DELETE options.
To use a :class:`.ForeignKeyConstraint`
that does not render or renders differently on MySQL, use a custom
compilation option. An example of this usage has been added to the
documentation, see :ref:`mysql_foreign_keys`.
[ticket:2721] [ticket:2839]
|
|
|
|
|
|
|
|
|
| |
if it was generated from a :class:`.Column` that didn't specify ``unique``
(where it defaults to ``None``). The flag will now always be ``True`` or
``False``. [ticket:2825]
Conflicts:
lib/sqlalchemy/sql/schema.py
|
|
|
|
| |
suddenly hitting this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This enables the subquery eager loader strategy to apply a DISTINCT
to the innermost SELECT subquery, to assist in the case where
duplicate rows are generated by the innermost query which corresponds
to this relationship (there's not yet a general solution to the issue
of dupe rows within subquery eager loading, however, when joins outside
of the innermost subquery produce dupes). When the flag
is set to ``True``, the DISTINCT is rendered unconditionally, and when
it is set to ``None``, DISTINCT is rendered if the innermost relationship
targets columns that do not comprise a full primary key.
The option defaults to False in 0.8 (e.g. off by default in all cases),
None in 0.9 (e.g. automatic by default). Thanks to Alexander Koval
for help with this. [ticket:2836]
Conflicts:
lib/sqlalchemy/orm/relationships.py
|
|
|
|
|
|
| |
query string to override those defaults set up in the connect,
including "buffered" and "raise_on_warnings".
[ticket:2515]
|
|
|
|
|
| |
rendered in the column list of a CREATE INDEX statement.
[ticket:2742]
|
|
|
|
|
|
|
|
|
|
|
| |
mssql to ensure that any literal SQL expression values are
rendered directly as literals, instead of as bound parameters,
within a CREATE INDEX statement. [ticket:2742]
- don't need expression_as_ddl(); literal_binds and include_table
take care of this functionality.
Conflicts:
lib/sqlalchemy/sql/util.py
|
|
|
|
|
|
|
|
|
| |
typically via in-place mutation, will raise an informative error
message rather than causing a recursion overflow.
[ticket:2815]
Conflicts:
lib/sqlalchemy/sql/selectable.py
|
|
|
|
|
|
|
|
|
|
| |
:func:`.foreign` on a :class:`.Column` before association with a parent
:class:`.Table` could produce issues related to the parent table not
rendering within joins, due to the inherent copy operation performed
by an annotation. [ticket:2813]
Conflicts:
lib/sqlalchemy/sql/elements.py
|
|
|
|
| |
raises a warning. Removed in 0.9. [ticket:2831]
|
|\
| |
| | |
Fix a typo: evaluted -> evaluated.
|
|/ |
|
|
|
|
| |
- break out into "production" and "experimental"
|
|
|
|
| |
- use match with a .* preceding instead of search
|
| |
|
|
|
|
| |
re.match to re.search
|
| |
|