| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I367baf75a1ac66149264bc94ba18be0076958e95
|
|
|
|
| |
Change-Id: Ia7d0ea7cc4389bc6adc4226efd5b18ecb68ffb2b
|
|
|
|
| |
Fixes #824
|
|
|
|
|
|
|
| |
Existence of a column check used ``ColumnCollection.contains_column`` with a
the name of the column instead of the column instance.
Change-Id: I41d9f6b6ed9e44eeb9ced78b039da6261491eeee
|
|
|
|
|
|
|
| |
Also add a in the pep8 tox job a check to verify that all files
are properly formatted
Change-Id: I7bac8463b273f3bce9be098e6ee76f1761e28e72
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A major rework of the "type comparison" logic is in place which changes the
entire approach by which column datatypes are compared. Types are now
compared based on the DDL string generated by the metadata type vs. the
datatype reflected from the database. This means we compare types based on
what would actually render and additionally if elements of the types change
like string length, those changes are detected as well. False positives
like those generated between SQLAlchemy Boolean and MySQL TINYINT should
also be resolved. Thanks very much to Paul Becotte for lots of hard work
and patience on this one.
Fixes: #605
Closes: #619
Pull-request: https://github.com/sqlalchemy/alembic/pull/619
Pull-request-sha: 1a6a3860881081c3b98fdbfc203f8d3af5f98926
Change-Id: I1ab30f2a30fc567cde56b5b8be5f521ff235b67b
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- The internal system for Alembic operations has been reworked to now
build upon an extensible system of operation objects. New operations
can be added to the ``op.`` namespace, including that they are
available in custom autogenerate schemes. fixes #302
- The internal system for autogenerate been reworked to build upon
the extensible system of operation objects present in #302.
A new customization hook process_revision_directives is added
to allow manipulation of the autogen stream. Fixes #301
|
| |
|
|
|
|
| |
- update the readme.unittests a bit
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
from a ``versions/`` directory now supports so-called
"sourceless" operation, where the ``.py`` files are not present
and instead ``.pyc`` or ``.pyo`` files are directly present where
the ``.py`` files should be. Note that while Python 3.3 has a
new system of locating ``.pyc``/``.pyo`` files within a directory
called ``__pycache__`` (e.g. PEP-3147), PEP-3147 maintains
support for the "source-less imports" use case, where the
``.pyc``/``.pyo`` are in present in the "old" location, e.g. next
to the ``.py`` file; this is the usage that's supported even when
running Python3.3. #163
|
|
|