| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
issue in pytest
|
| | |
|
| |
|
|
| |
- get dropfirst to work around missing schemas
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
getting them all compatible with py.test as well
|
| | |
|
| |
|
|
|
| |
an issue with utf8, and this should be part of the testing URL in any case.
if we observe failures on some drivers/etc. this can become a "requires"
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
- alter the plugin/requirements system to support multiple --db/--dburi
options. The first option serves as the "default" database, and the
subsequent ones serve as "available" databases. the requirement
rules at the *class level only* now search among the "available" databases
in order to run per-database test suites at once. rationale is to support
using the test plugin system under Alembic as well, which already
takes advantage of multiple database tests.
|
| | |
|
| | |
|
| |
|
|
|
| |
- break out reflection of views to support view column reflection separately
from view definition
|
| |
|
|
| |
both _resolve_type_affinity() directly as well as round trip tests fully.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fully usable within declarative relationship configuration, as its
string classname would not be available in the registry of classnames
at mapper configuration time. The class now explicitly adds itself
to the class regsitry, and additionally both :class:`.AbstractConcreteBase`
as well as :class:`.ConcreteBase` set themselves up *before* mappers
are configured within the :func:`.configure_mappers` setup, using
the new :meth:`.MapperEvents.before_configured` event. [ticket:2950]
- Added new :meth:`.MapperEvents.before_configured` event which allows
an event at the start of :func:`.configure_mappers`, as well
as ``__declare_first__()`` hook within declarative to complement
``__declare_last__()``.
- modified how after_configured is invoked; we just make a dispatch()
not actually connected to any mapper. this makes it easier
to also invoke before_configured correctly.
- improved the ComparableEntity fixture to handle collections that are sets.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
applied to :class:`.Constraint` and :class:`.Index` objects. Based
on a recipe in the wiki, the new feature uses schema-events to set up
names as various schema objects are associated with each other. The
events then expose a configuration system through a new argument
:paramref:`.MetaData.naming_convention`. This system allows production
of both simple and custom naming schemes for constraints and indexes
on a per-:class:`.MetaData` basis. [ticket:2923]
commit 7e65e52c086652de3dd3303c723f98f09af54db8
Author: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Sat Feb 1 15:09:04 2014 -0500
- first pass at new naming approach
|
| | |
|
| |
|
|
| |
other tests to fail
|
| |
|
|
| |
- test_autoincrement_col still needs reflection overall
|
| |
|
|
|
|
| |
double close
- ensure no iterator changed size issues in testing.engines
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
_reset_agent, so that it's local to the various begin_impl(),
rollback_impl(), etc. this allows setting/resetting of the flag
to be symmetric.
- don't set _reset_agent if it's not None, don't unset it if it isn't
our own transaction.
- make sure we clean it out in close().
- basically, we're dealing here with pools using "threadlocal" that have a
counter, other various mismatches that the tests bring up
- test for recover() now has to invalidate() the previous connection,
because closing it actually rolls it back (e.g. this test was relying
on the broken behavior).
|
| | |
|
| | |
|
| |
|
|
| |
- update a few exclusions to support current pymssql. passes all of test_suite and dialect/mssql
|
| |
|
|
|
| |
- wrangle through osx+pyodbc+freetds to get at least test_suite to pass again
with mssql+pyodbc. invovled adding some silly requirements
|
| | |
|
| | |
|
| |
|
|
|
|
| |
that the lists
of each can be reflected independently. Testing [ticket:2898] at the moment.
|
| | |
|
| |
|
|
| |
__only_on__ attribute
|
| |
|
|
|
| |
- implement Query with_for_update()
- rework docs and tests
|
| |
|
|
|
|
|
|
|
|
| |
Python ``Decimal`` via string is now configurable. The
flag ``decimal_return_scale`` is now supported by all :class:`.Numeric`
and :class:`.Float` types, which will ensure this many digits are taken
from the native floating point value when it is converted to string.
If not present, the type will make use of the value of ``.scale``, if
the type supports this setting and it is non-None. Otherwise the original
default length of 10 is used. [ticket:2867]
|
| | |
|
| |
|
|
|
| |
correctly with table or column names that contain non-ASCII
characters. [ticket:2869]
|
| | |
|
| |
|
|
| |
round it
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
e.g. values that are normally bound parameters but due to context must
be rendered as strings, typically within DDL constructs such as
CHECK constraints and indexes (note that "literal bind" values
become used by DDL as of :ticket:`2742`). A new method
:meth:`.TypeEngine.literal_processor` serves as the base, and
:meth:`.TypeDecorator.process_literal_param` is added to allow wrapping
of a native literal rendering method. [ticket:2838]
- enhance _get_colparams so that we can send flags like literal_binds into
INSERT statements
- add support in PG for inspecting standard_conforming_strings
- add a new series of roundtrip tests based on INSERT of literal plus SELECT
for basic literal rendering in dialect suite
|
| |
|
|
|
|
|
| |
behavior as that of :class:`.mysql.ENUM`. Quotes are not required when
setting up the value, but quotes that are present will be auto-detected
along with a warning. This also helps with Alembic where
the SET type doesn't render with quotes. [ticket:2817]
|
| |
|
|
| |
- callcount
|
| |
|
|
|
|
| |
--write-profiles is set
- some sqlite callcounts
|