| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
- add tests for extension APIs
- add a render helper function
- lots of docs
|
| |
|
|
|
|
|
|
| |
- add ExecuteSQLOp
- use cls within @classmethod for portability
- more docs
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- docs
- start refactoring new module plugin system
|
| |
|
|
|
|
| |
- all tests pass
|
| |
|
| |
|
| |
|
|
|
|
| |
completely. One test works, test_render_add_index_schema.
|
|
|
|
| |
legacy decorators in case of kw use
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
alembic/autogenerate/__init__.py
alembic/command.py
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
for now
|
| |
| |
| |
| | |
the operations package but not break all of impl
|
| |
| |
| |
| | |
now leaning towards, "very separate"
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- need to finally clean up autogenerate tests if we're to start
really altering the flow
- think more about the operations we'll want to represent. These likely
should match most closely to autogenerate's flow; as far as linking to
operations, we should be able to pass them through to an impl. the actual Operations
methods are factories for the API objects.
|
| | |
|
| | |
|
|/
|
|
|
|
| |
backwards compat for major import targets. command and config
are too front-facing for a move like this so leave them
as is. first part of #302
|
|
|
|
|
|
|
|
| |
versioning refactor in 0.7 as a more granular version of
:func:`.command.stamp`, now includes the "create the alembic_version
table if not present" step in the same way as the command version,
which was previously omitted.
fixes #300
|
|
|
|
| |
warnings
|
|
|
|
|
|
|
| |
"ondelete" would not render within the ``op.create_foreign_key()``
directive, even though they render within a full
``ForeignKeyConstraint`` directive.
fixes #298
|
| |
|
| |
|
|\
| |
| |
| | |
Fix typo in autogenerate documentation
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
have the identical set of ancestor revisions would fail to be
upgradable, producing an assertion failure. Merge points were
previously assumed to always require at least an UPDATE in
alembic_revision from one of the previous revs to the new one,
however in this case, if one of the mergepoints has already
been reached, the remaining mergepoints have no row to UPDATE therefore
they must do an INSERT of their target version.
fixes #297
|
| |
|
|
|
|
|
|
|
|
| |
environment, but also present on the custom types themselves, by
supplying a method ``compare_against_backend``.
Added a new documentation section :ref:`compare_types` describing
type comparison fully.
fixes #296
|
|\
| |
| |
| | |
- fixed spelling mistake in docs
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
:paramref:`.EnvironmentContext.configure.literal_binds`, which
will pass the ``literal_binds`` flag into the compilation of SQL
constructs when using "offline" mode. This has the effect that
SQL objects like inserts, updates, deletes as well as textual
statements sent using ``text()`` will be compiled such that the dialect
will attempt to render literal values "inline" automatically.
Only a subset of types is typically supported; the
:meth:`.Operations.inline_literal` construct remains as the construct
used to force a specific literal representation of a value.
The :paramref:`.EnvironmentContext.configure.literal_binds` flag
is added to the "offline" section of the ``env.py`` files generated
in new environments.
fixes #255
- enhance the op_fixture as well as MigrationContext._stdout_connection()
so that it uses the real DefaultImpl
and MigrationContext fully in tests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
:paramref:`~.Operations.batch_alter_table.copy_from` parameter for
batch mode, which previously was not functioning. This allows
"batch mode" to be usable in conjunction with ``--sql``.
fixes #289
- sqlite dialect checks for "create_index" and "drop_index" as exceptions
for "recreate" in batch mode, the same way as "add_column", so that
unnecessary table recreates don't emit for index-only operations
|
| |
|
|
|
|
|
|
| |
directive, which was mis-named internally such that the operation
within a batch context could not proceed.
fixes #287
|
|
|
|
| |
don't have this right. up to post2
|
| |
|