| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
event.listen and event.listen_for have a kwarg once added in 0.9.4 (not 0.9.3) CHANGELOG agrees with this as well. (as does my manual testing)
|
| |
|
|
|
| |
and the current approach used for sections is not able to work for fine-grained
anchors like these, another approach needs to be taken.
|
| |
|
|
|
|
|
|
|
|
|
| |
scenario, where an INSERT/DELETE can be turned into an UPDATE.
In this situation, a many-to-one relationship set to None, or
in some cases a scalar attribute set to None, may not be detected
as a net change in value, and therefore the UPDATE would not reset
what was on the previous row. This is due to some as-yet
unresovled side effects of the way attribute history works in terms
of implicitly assuming None isn't really a "change" for a previously
un-set attribute. See also :ticket:`3061`. fixes #3060
|
| |
|
|
|
|
|
|
|
|
| |
- reduce the real estate for the top nav; move the search box
into the top yellow box, close in space
- use a new CSS/js approach such that the top toolbar freezes from
scrolling at the top of the page. The left nav scrolls independently
of the content pane so that the local contents remain visible regardless
of scrolling. this approach is disabled on mobile where the dual scrollbars
may be cumbersome (overall the site is not well designed for mobile).
|
| |
|
|
|
| |
UNION would wrap the union in an anonymous (e.g. unlabled) subquery.
fixes #3044
|
| |
|
|
|
|
| |
is needed to allow the ORM to skip over trying to "hash" an ORM-mapped
HSTORE column when requesting it in a mixed column/entity list.
Patch courtesy Gunnlaugur Þór Briem. Fixes #3053
|
| |
|
|
|
|
|
| |
eager loads across a polymorphic-subclass boundary in conjunction
with polymorphic loading would fail to locate the subclass-link in the
chain, erroring out with a missing property name on an
:class:`.AliasedClass`. fixes #3055
|
| |
|
|
|
|
| |
due to repeats would not correctly be rewritten in subqueries.
This would affect SELECT queries with any kind of subquery + join.
fixes #3057
|
| | |
|
| |
|
|
|
|
|
| |
:meth:`.Operators.__or__` and :meth:`.Operators.__invert__`
operator overload methods could not be overridden within a custom
:class:`.TypeEngine.Comparator` implementation.
fixes #3012
|
| |
|
|
|
|
|
|
|
| |
filter operators section
- add language to MATCH explicitly stating this operator varies by backend and is not available
on SQLite, as the tutorial defaults to SQLite to start with, fix #3059
- on the actual match() documentation fix this up to be more accurate, list some example renderings
for different backends. again mention SQLite not supported
|
| |
|
|
| |
- add new FAQ for rendering SQL as a string
|
| |
|
|
| |
legacy
|
| |
|
|
|
| |
- refactor tests a bit
fixes #2785
|
| |\
| |
| |
| | |
https://bitbucket.org/LevonXXL/sqlalchemy/overview into t
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
- add the query profiling recipe, fix it with a stack as we now nest those
calls occasionally
- tabs to spaces
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
Add note on PostgreSQL config for test runs
|
| | |/ /
| | |
| | |
| | |
| | | |
Several tests on PostgreSQL depend on English-language text search
config being the default in the test DB. This adds a note about that.
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | | |
report change events for the ``setdefault()`` dictionary operation.
fixes #3051
|
| | |\ \ |
|
| |\ \ \ \
| |/ / /
| | / /
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
move the insert rows article there as well
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
request #17)
Posgtresql -> PostgreSQL
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
Added optional '=' to MySQL KEY_BLOCK_SIZE regex
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Documentation fix-up: "its" vs. "it's"
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Removed ungrammatical apostrophes from documentation, replacing
"it's" with "its" where appropriate (but in a few cases with "it is"
when that read better).
While doing that, I also fixed a couple of minor typos etc.
as I noticed them.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
AttributeErrors or KeyErrors that should raise during mapper
configuration due to user errors. The catch for attribute/keyerror
has been made more specific to not include the configuration step.
fixes #3047
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a connection invalidation could occur within an already critical section
like a connection.close(); ultimately, these conditions are caused
by the change in :ticket:`2907`, in that the "reset on return" feature
calls out to the Connection/Transaction in order to handle it, where
"disconnect detection" might be caught. However, it's possible that
the more recent change in :ticket:`2985` made it more likely for this
to be seen as the "connection invalidate" operation is much quicker,
as the issue is more reproducible on 0.9.4 than 0.9.3.
Checks are now added within any section that
an invalidate might occur to halt further disallowed operations
on the invalidated connection. This includes two fixes both at the
engine level and at the pool level. While the issue was observed
with highly concurrent gevent cases, it could in theory occur in
any kind of scenario where a disconnect occurs within the connection
close operation.
fixes #3043
ref #2985
ref #2907
- add some defensive checks during an invalidate situation:
1. _ConnectionRecord.invalidate might be called twice within finalize_fairy
if the _reset() raises an invalidate condition, invalidates, raises and then
goes to invalidate the CR. so check for this.
2. similarly within Conneciton, anytime we do handle_dbapi_error(), we might become invalidated.
so a following finally must check self.__invalid before dealing with the connection
any futher.
|
| | |/
|/|
| |
| |
| |
| |
| | |
would produce an empty WHERE clause when an empty :func:`.and_()`
or :func:`.or_()` or other blank expression were applied. This is
now consistent with that of :func:`.select`.
fixes #3045
|
| | |
| |
| |
| |
| |
| | |
__init__() method.
No clue. nosetests doesn't do this. concerning that other tests might have the same issue.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
"SELECT FIRST n ROWS" using a bound parameter (only firebird has both),
combined with column-level subqueries
which also feature "limit" as well as "positional" bound parameters
(e.g. qmark style) would erroneously assign the subquery-level positions
before that of the enclosing SELECT, thus returning parameters which
are out of order. Fixes #3038
|
| | |
| |
| |
| | |
Found using: https://github.com/intgr/topy
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Added some links in session docs
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a join condition that is strictly from a single column to itself,
translated through some kind of SQL function or expression. This
is kind of experimental, but the first proof of concept is a
"materialized path" join condition where a path string is compared
to itself using "like". The :meth:`.Operators.like` operator has
also been added to the list of valid operators to use in a primaryjoin
condition. fixes #3029
|
| |/
|
|
|
|
|
| |
specify a :func:`.text` expression as the target; the index no longer
needs to have a table-bound column present if the index is to be
manually added to the table, either via inline declaration or via
:meth:`.Table.append_constraint`. fixes #3028
|
| |
|
|
|
|
|
| |
to use the ``database_principal_id()`` function in conjunction with
the ``sys.database_principals`` view so that we can determine
the default schema independently of the type of login in progress
(e.g., SQL Server, Windows, etc). fixes #3025
|
| |
|
|
|
| |
adding an argument for a construct not previously included for any
special arguments would fail. fixes #3024
|
