| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
exposes it
|
| |
|
|
|
|
|
|
|
| |
all known cases is provided by :class:`.DefaultDialect`, has been
tightened to expect ``include_columns`` and ``exclude_columns``
arguments without any kw option, reducing ambiguity - previously
``exclude_columns`` was missing. [ticket:2748]
|
|
|
|
|
|
| |
typically via in-place mutation, will raise an informative error
message rather than causing a recursion overflow.
[ticket:2815]
|
|
|
|
|
|
|
| |
: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]
|
| |
|
|
|
|
|
| |
object. this was an accidental commit that did nothing; a warning is raised
in 0.8.3 when this kw arg is used. [ticket:2831]
|
| |
|
|
|
|
| |
entity returns without otherwise changing much [ticket:2824]
|
| |
|
| |
|
|
|
|
| |
well. this probably has some bugs
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The system of loader options has been entirely rearchitected to build
upon a much more comprehensive base, the :class:`.Load` object. This
base allows any common loader option like :func:`.joinedload`,
:func:`.defer`, etc. to be used in a "chained" style for the purpose
of specifying options down a path, such as ``joinedload("foo").subqueryload("bar")``.
The new system supersedes the usage of dot-separated path names,
multiple attributes within options, and the usage of ``_all()`` options.
- Added a new load option :func:`.orm.load_only`. This allows a series
of column names to be specified as loading "only" those attributes,
deferring the rest.
|
|
|
|
|
|
| |
name is already an instance of _anonymous_label(), we don't downgrade
it to a plain quoted_name - fixes regression from [ticket:2812].
[ticket:2834]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of groups of column expressions to a :class:`.Query` construct.
The group of columns are returned as a single tuple by default. The
behavior of :class:`.Bundle` can be overridden however to provide
any sort of result processing to the returned row. One example included
is :attr:`.Composite.Comparator.bundle`, which applies a bundled form
of a "composite" mapped attribute.
[ticket:2824]
- The :func:`.composite` construct now maintains the return object
when used in a column-oriented :class:`.Query`, rather than expanding
out into individual columns. This makes use of the new :class:`.Bundle`
feature internally. This behavior is backwards incompatible; to
select from a composite column which will expand out, use
``MyClass.some_composite.clauses``.
|
|
|
|
| |
- break out into "production" and "experimental"
|
|
|
|
| |
into account the id() of the function itself and self, [ticket:2832]
|
|
|
|
| |
- use match with a .* preceding instead of search
|
| |
|
|\ |
|
| |\
| | |
| | | |
re.match to re.search
|
| | |
| | |
| | |
| | |
| | | |
Convert to re.search to eliminate the restriction on only matching the
beginning of the string
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Hide password in URL and Engine __repr__
|
| |/
| |
| |
| | |
Fixes #2821
|
|\ \
| | |
| | | |
Replace a big loop + dict lookup in Connection.execute() with a simple visitor pattern
|
|/ /
| |
| |
| | |
pattern
|
| | |
|
| | |
|
| |
| |
| |
| | |
changelog once
|
|/
|
|
|
| |
version id programmatically outside of the generator. using this system,
we can also leave the version id alone.
|
|
|
|
| |
filters applied.
|
| |
|
| |
|
|
|
|
| |
in-python only cols
|
|
|
|
|
|
| |
of the incoming :class:`.Column` would prevent primary key constraints,
indexes, and foreign key constraints from being correctly reflected.
Also in 0.8.3. [ticket:2811]
|
|
|
|
| |
- callcount
|
| |
|
| |
|
|
|
|
| |
quoting the lowercase name.
|
|
|
|
|
|
| |
--write-profiles is set
- some sqlite callcounts
|
| |
|
|
|
|
| |
- cx_oracle dialect doesn't use normal col names, lets just not rely on that for now
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of relying upon various ``quote=True`` flags being passed around,
these flags are converted into rich string objects with quoting information
included at the point at which they are passed to common schema constructs
like :class:`.Table`, :class:`.Column`, etc. This solves the issue
of various methods that don't correctly honor the "quote" flag such
as :meth:`.Engine.has_table` and related methods. The :class:`.quoted_name`
object is a string subclass that can also be used explicitly if needed;
the object will hold onto the quoting preferences passed and will
also bypass the "name normalization" performed by dialects that
standardize on uppercase symbols, such as Oracle, Firebird and DB2.
The upshot is that the "uppercase" backends can now work with force-quoted
names, such as lowercase-quoted names and new reserved words.
[ticket:2812]
|
|
|
|
| |
unittest.TestCase
|