| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
than line length
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
- update the readme.unittests a bit
|
|\
| |
| | |
replacing eval in multidb template with globals() function lookup
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
:meth:`.Operations.create_index` directive. Within the list of columns,
the SQLAlchemy ``text()`` construct can be sent, embedding a literal
SQL expression; the :meth:`.Operations.create_index` will perform some hackery
behind the scenes to get the :class:`.Index` construct to cooperate.
This works around some current limitations in :class:`.Index`
which should be resolved on the SQLAlchemy side at some point.
fixes #222
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
paradoxxxzero/alembic/paradoxxxzero/fix-sorted-of-none-values-in-compare-for-1403597500844 (pull request #23)
Fix sorted of None values in compare for python 3
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
working better across platforms and expressions, in particular on
the Postgresql backend, mostly dealing with quoting/not quoting of various
expressions at the appropriate time and on a per-backend basis.
Repaired and tested support for such defaults as Postgresql interval
and array defaults.
fixes #212
|
| |
| |
| |
| |
| |
| | |
the output now prefixes the string with ``"FAILED:"``, and the error
is also written to the log output using ``log.error()``.
fixes #209
|
| |
| |
| |
| |
| |
| |
| | |
counted in autogenerate as "drops"; this time it's been reported
that an implicitly created index might be named the same as a composite
foreign key constraint, and not the actual columns, so we now skip those
when detected as well. fixes #208
|
|/
|
|
|
|
|
|
|
| |
to MigrationContext.configure
Using a mutable type as a default value is a common source of obscure
problems.
See
http://docs.python-guide.org/en/latest/writing/gotchas/#mutable-default-arguments
|
| |
|
|\
| |
| |
| | |
https://github.com/msabramo/alembic into t
|
| |
| |
| |
| |
| |
| |
| |
| | |
This lets migrations do stuff like:
op.get_context().config.get_main_option('schema')
where `schema` is a custom option that I added to alembic.ini
|
|\ \
| |/
|/| |
.gitignore: .egg-info => *.egg-info
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
includes an Index with the same name as a column, autogenerate reported
it as an "add" even though its not; this is because we ignore reflected
indexes of this nature due to MySQL creating them implicitly. Indexes
that are named the same as a column are now ignored on
MySQL if we see that the backend is reporting that it already exists;
this indicates that we can still detect additions of these indexes
but not drops, as we cannot distinguish a backend index same-named
as the column as one that is user generated or mysql-generated.
fixes #202
|
| |
|
|
|
|
|
|
|
|
|
|
| |
:paramref:`.EnvironmentContext.configure.transaction_per_migration`,
which when True causes the BEGIN/COMMIT pair to incur for each migration
individually, rather than for the whole series of migrations. This is
to assist with some database directives that need to be within individual
transactions, without the need to disable transactional DDL entirely.
fixes #201
|
|
|
|
|
|
|
|
| |
the original :class:`.Column` object when evaluating a database-only
column to be dropped; the object would not include the parent
:class:`.Table` nor other aspects of the column that are important
for generating the "downgrade" case where the column is recreated.
fixes #200
|
|
|
|
|
| |
would fail if the :class:`.Config` in use didn't actually
originate from a command line call. fixes #195
|
|
|
|
|
|
|
| |
from :ticket:`183`, where add_index()
drop_index() directives would not correctly render the ``f()``
construct when the index contained a convention-driven name.
fixes #194 re: #183
|
| |
|
| |
|
|
|
|
|
|
|
| |
drop any existing server defaults or constraints when the
:paramref:`.drop_column.mssql_drop_check` or
:paramref:`.drop_column.mssql_drop_default`
arguments are used. fix #186
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
which will now be rendered if only the server default is changing
or being dropped (e.g. specify None to alter_column() to indicate
"DROP DEFAULT"). Also added support for rendering MODIFY rather than
CHANGE when the column name isn't changing.
fixes #103
|
| |
|