| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
adjust its top within the initial scroll period, this is what foundationdb
is doing. For whatever reason that comes out smooth on all browsers.
the rationale is so that its independently scrollable at all times.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
causing the issue
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
works in chrome + safari
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / / |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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).
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- 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
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
- fix a bad comparison in MySQL w/ limit/offset thing
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
add to lazy loading.
not really clear which approach is better in the long run.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
- restore __len__ to identity map
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
: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
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
- implement for SQL server, use window functions when simple limit/offset not available
|
| | |\ \ \ \
| | |_|_|/
| |/| | |
| | | | | |
https://bitbucket.org/dobesv/sqlalchemy/branch/issue_3034 into ticket_3034
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
inefficient select._offset and select._limit operations.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
a BindParameter, instead of _offset and _limit in GenerativeSelect.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
on a query.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
legacy
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 72a09d9e5c54e3ee8b3561da144d8379ce1df747.
|