| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Found using: https://github.com/intgr/topy
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
| |
be used to manufacture objects that behave as though they were loaded
from a session, then detached. Attributes that aren't present
are marked as expired, and the object can be added to a Session
where it will act like a persistent one. fix #3017
|
| |
|
|
| |
being documented
|
| | |
|
| |
|
|
| |
to accept things flexibly), fix #2999
|
| |
|
|
|
|
|
|
|
|
|
| |
1. fix the typo in the paragraph, fixes #2998
2. as zope-sqlalchemy only provides transaction integration and not session scoping,
dial back the language here as people are probably using scoped_session with pyramid anyway
3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard,
take out the word "strongly" from the recommendation.
4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy
layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks"
(by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway")
|
| |\
| |
| |
| | |
https://github.com/charlax/sqlalchemy
|
| | |
| |
| |
| | |
Most linter complain when comparing with None.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
| |
The selectable is the third argument to with_polymorphic.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
sections
- convert all paramter references in relationship documentation to :paramref:
|
| | |
|
| |
|
|
| |
- trim off fn prefix on some relationship parameter names
|
| |
|
|
|
|
| |
flag allows a custom op from :meth:`.Operators.op` to be considered
as a "comparison" operator, thus usable for custom
:paramref:`.relationship.primaryjoin` conditions.
|
| |
|
|
| |
and modernize the engines chapter a bit
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
target of :paramref:`.relationship.secondary` for the purposes
of creating very complex :func:`.relationship` join conditions.
The change includes adjustments to query joining, joined eager loading
to not render a SELECT subquery, changes to lazy loading such that
the "secondary" target is properly included in the SELECT, and
changes to declarative to better support specification of a
join() object with classes as targets.
|
| | |
|
| |
|
|
|
| |
The text refers to ``boston_addresses``, while the code sample uses
``addresses``.
|
| | |
|
| |
|
|
|
| |
- make section title actually say, "such as for test suites"
- add topic section detailing an evented approach to allowing ROLLBACK by using savepoint
|
| | |
|
| | |
|
| |
|
| |
This makes the code block more consistent with the preceding one and also prevents the variable from being colored as a builtin (which `object` is) during syntax highlighting.
|
| |
|
|
| |
the primaryjoin examples there
|
| |
|
|
|
|
|
| |
:func:`.validates` function; when set to False, a validation event
will not be triggered if the event was initated as a backref to
an attribute operation from the other side. [ticket:1535]
- break out validation tests into an updated module test_validators
|
| |
|
|
|
|
|
|
| |
standalone gendered pronoun with a gender-neutral subject, but also
have replaced all occurences of "his/her", "his or her", etc. The docs have always
strived to account for both genders in any non-specific singular pronoun,
however recent controversy in the community suggests
that a zero-gendered-pronoun policy is probably best going forward.
|
| |
|
|
| |
- add glossary terms
|
| |
|
|
|
| |
are still useful, just include notes that for more complex descriptor operations,
hybrids are probably preferable
|
| |
|
|
|
| |
- add the other versioning examples from the wiki
- modernize the dictlike examples
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
