| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Most linter complain when comparing with None.
|
| | |
|
| |
|
|
|
| |
"true" / "false" or "1" / "0".
- added Boolean tests to the test suite
|
| |
|
|
| |
SQLA internal tests outside; plus things like savepoints, twophase
|
| | |
|
| | |
|
| |
|
|
|
|
| |
suite
and adding some more requirements
|
| |
|
|
|
|
|
|
| |
mark a constraint name as already having had a naming convention applied.
This token will be used by Alembic migrations as of Alembic 0.6.4
in order to render constraints in migration scripts with names marked
as already having been subject to a naming convention.
re: #2991
|
| |
|
|
|
|
| |
apply to :class:`.CheckConstraint` objects that are associated
directly with a :class:`.Column` instead of just on the
:class:`.Table`.
|
| |
|
|
|
|
|
|
|
| |
where the name of a check constraint making use of the
`"%(constraint_name)s"` token would get doubled up for the
constraint generated by a boolean or enum type, and overall
duplicate events would cause the `"%(constraint_name)s"` token
to keep compounding itself.
fixes #2991
|
| |
|
|
| |
honor it unless nose is imported too...
|
| | |
|
| |
|
|
|
|
| |
or :meth:`.MapperEvents.after_configured` events are applied to a
specific mapper or mapped class, as the events are only invoked
for the :class:`.Mapper` target at the general level.
|
| |
|
|
|
| |
and :func:`.event.listens_for`. This is a convenience feature which
will wrap the given listener such that it is only invoked once.
|
| |\
| |
| | |
Fixes argument number in docs
|
| |/
|
| |
The selectable is the third argument to with_polymorphic.
|
| | |
|
| |\
| |
| | |
Update URL for pymssql
|
| | |
| |
| |
| | |
@zzzeek.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
approach
should be taken
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
and also will fail on py3k.
- enhance exclusions so that a requirement attribute can be passed
to fails_if/skip_if.
- fix coverage docs to mention pytest.
|
| | |
| |
| |
| |
| | |
- various improvemnts to oracle docs, rewrite section on unicode, more linking,
enhance section on resolve_synonyms
|
| |\ \ |
|
| | |/
| |
| |
| | |
This feature is now turned off by default.
|
| | |
| |
| |
| |
| | |
connection to be returned might get inadvertently cleaned out during
the "cleanup" process. Patch courtesy jd23.
|
| | | |
|
| | |
| |
| |
| | |
let's stay on the fence.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
(e.g. ``x[:] = [...]``) would fail on Py3k.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
is currently being supported in addition to nose, and will likely
be preferred to nose going forward. The nose plugin system used
by SQLAlchemy has been split out so that it works under pytest as
well. There are no plans to drop support for nose at the moment
and we hope that the test suite itself can continue to remain as
agnostic of testing platform as possible. See the file
README.unittests.rst for updated information on running tests
with pytest.
The test plugin system has also been enhanced to support running
tests against mutiple database URLs at once, by specifying the ``--db``
and/or ``--dburi`` flags multiple times. This does not run the entire test
suite for each database, but instead allows test cases that are specific
to certain backends make use of that backend as the test is run.
When using pytest as the test runner, the system will also run
specific test suites multiple times, once for each database, particularly
those tests within the "dialect suite". The plan is that the enhanced
system will also be used by Alembic, and allow Alembic to run
migration operation tests against multiple backends in one run, including
third-party backends not included within Alembic itself.
Third party dialects and extensions are also encouraged to standardize
on SQLAlchemy's test suite as a basis; see the file README.dialects.rst
for background on building out from SQLAlchemy's test platform.
|
| | |
| |
| |
| |
| | |
methods, classes, builtins, functools.partial(), everything known so far
- use get_callable_argspec() within ColumnDefault._maybe_wrap_callable, re: #2979
|
| | |
| |
| |
| |
| |
| | |
in particular the logic used to wrap "column default" callables
wouldn't work properly for Python built-ins.
fixes #2979
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
- break out reflection of views to support view column reflection separately
from view definition
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to specify the string ``"nested"``. When set to ``"nested"`` as opposed
to ``True``, the "chaining" of joins will parenthesize the inner join on the
right side of an existing outer join, instead of chaining as a string
of outer joins. This possibly should have been the default behavior
when 0.9 was released, as we introduced the feature of right-nested
joins in the ORM, however we are keeping it as a non-default for now
to avoid further surprises.
fixes #2976
|
| |/
|
|
|
|
|
|
|
|
|
| |
the first SQL expression would be applied as the "comparison type"
to a compared tuple value; this has the effect in some cases of an
inappropriate "type coersion" occurring, such as when a tuple that
has a mix of String and Binary values improperly coerces target
values to Binary even though that's not what they are on the left
side. :func:`.tuple_` now expects heterogeneous types within its
list of values.
fixes #2977
|
| |
|
|
|
|
| |
identity
isn't appended to the list. reflection makes use of this.
|
| |
|
|
|
|
|
|
|
| |
caused a user-provided "getter" to no longer receive values of ``None``
when fetching scalar values from a target that is non-present. The
check for None introduced by this change is now moved into the default
getter, so a user-provided getter will also again receive values of
None.
re: #2810
|
| |
|
|
|
|
| |
refreshed with current names, so that an ``import *`` from this
module again works.
fixes #2975
|
