| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
to include use_alter argument, if present.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change does not affect to any behaviors of it, but is just stylish
improvements to remove 2to3 dependency.
1. All old-style absolute imports e.g. `from alembic import util` are
replaced by relative imports e.g. `from . import util`.
2. Use of proxy modules (`alembic.op` and `alembic.context`) are replaced
by deferred import patterns, but these modules still exist.
3. Imports are grouped by 3 types of their origins (standard libraries,
third party libraries, and local modules) and blank lines are put between
each group of imports. This style is from PEP 8:
<http://www.python.org/dev/peps/pep-0008/#imports>
For stylish change, I can't do that much, because it was intentionally done
as it was by the author. If the author will allow me to make it more closer
to PEP 8 style, I will do that as well.
|
| |
|
|
|
|
| |
defaults here
|
|
|
|
|
|
| |
arguments like "mysql_engine" and others within
op.create_table().
#110
|
|
|
|
|
|
|
|
| |
can be customized, in particular to allow special rendering
for user-defined column, constraint subclasses, using new
``render_item`` argument to
:meth:`.EnvironmentContext.configure`.
#108
|
|
|
|
|
| |
to be added to a table made use of the ".key" paramter.
#99
|
|
|
|
|
|
|
|
|
|
| |
when "setup.py test" is run, #96
- add version detection for 0.8, apply this version detection to
test_autogenerate:AutogenRenderTest.test_render_fk_constraint_kwarg
and emit explicit append_constraint() for each FK if not on 0.8 as FKs
do not auto-attach in 0.7, #96
- add a README containing instructions for running tests and setting up
optional database backens, #96
|
|
|
|
|
|
| |
ForeignKeyConstraint options onupdate,
ondelete, initially, and deferred.
#92
|
|
|
|
|
|
|
| |
in the rendered table metadata
if this flag was set to false on the source
:class:`.Column` object.
#94
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
has been added fully to all operations, as well as to
the autogenerate feature. When using autogenerate,
specifying the flag include_schemas=True to
Environment.configure() will also cause autogenerate
to scan all schemas located by Inspector.get_schema_names(),
which is supported by *some* (but not all)
SQLAlchemy dialects including Postgresql.
*Enormous* thanks to Bruno Binet for a huge effort
in implementing as well as writing tests. #33.
|
|\ |
|
| |
| |
| |
| | |
for some reasons one of the new tests fails
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
EnvironmentContext.configure(),
specifies a callable which will include/exclude tables
in their entirety from the autogeneration process
based on name. #27
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
render create_table() on the upgrade side for a
table that has a Boolean type, an unnecessary
CheckConstraint() would be generated. #58
- [feature] Implemented SQL rendering for
CheckConstraint() within autogenerate upgrade,
including for literal SQL as well as SQL Expression
Language expressions.
|
|
|
|
| |
sensitive towards
|
| |
|
|
|
|
| |
in autogenerate, courtesy Atsushi Odagiri
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- [general] The focus of 0.3 is to clean up
and more fully document the public API of Alembic,
including better accessors on the MigrationContext
and ScriptDirectory objects. Methods that are
not considered to be public on these objects have
been underscored, and methods which should be public
have been cleaned up and documented, including:
MigrationContext.get_current_revision()
ScriptDirectory.iterate_revisions()
ScriptDirectory.get_current_head()
ScriptDirectory.get_heads()
ScriptDirectory.get_base()
ScriptDirectory.generate_revision()
- [feature] Added a bit of autogenerate to the
public API in the form of the function
alembic.autogenerate.compare_metadata.
|
|
|
|
| |
before their dependant tables. Also added the respective tests.
|
|
|
|
| |
regression from 0.2.0 [#26]
|
|
|
|
|
|
|
|
|
|
|
|
| |
now be customized to be some combination
of "rev id" and "slug", the latter of which
is based on the revision message.
By default, the pattern "<rev>_<slug>"
is used for new files. New script files
should include the "revision" variable
for this to work, which is part of
the newer script.py.mako scripts.
[#24]
|
|
|
|
| |
miraculous
|
|
|
|
| |
ForeignKeyConstraint.
|
|
|
|
|
|
|
|
|
| |
directives is "op.", matching the
mako templates. [#18]
- [feature] Add alembic_module_prefix argument
to configure() to complement
sqlalchemy_module_prefix. [#18]
|
|
|
|
|
|
| |
correct reflection of a foreign-key
referenced table in the list of "to remove".
[#16]
|
|
|
|
|
| |
generated between the two comments
if no net migrations were present.
|
|
|
|
|
|
| |
file handles are closed.
- PyPy is supported.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
areas
- add "requires 07" decorators to test suite
- add tests for PG ENUM in offline mode. works in conjunction
with the latest 0.7.4 tip of SQLAlchemy, fixes #9. Docs will
be needed to illustrate how ENUM should be used.
- add support for table before_create and after_create events
within op.create_table(). Currently this will do the ENUM
thing for PG but will also invoke any other kinds of events
that might get configured on the table.
|
| |
|
|
|
|
|
|
|
| |
autogenerate_sqlalchemy_prefix
to sqlalchemy_module_prefix
- add create_check_constraint() directive
|
|
|
|
|
|
|
|
|
|
|
|
| |
PG context in particular does some tricks to help these.
- But since type/default comparison is still loaded with surprises,
particularly the MySQL/MSSQL TINYINT/BIT-> boolean thing which we
can work around but haven't yet, turn both off by default. They
aren't super useful compared to the huge number of wrong results
they can currently emit.
- Also add a plugin system for type/server default comparison.
- everything works but we're coding way ahead of tests at this
point
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
multiple changes to a single col are collapsed
into one step, will work for other dialects
which may support this too
- add support for "imports" in scripts so
that dialect-specific types can be rendered straight in
from their parent module and work immediately
- rework the internals of autogenerate to be more
succinct, though there's a lot more that could
happen here to make this easier
|
|
|
|
| |
this before releasing
|
|
|
|
| |
- add an alter column autogen test with an FK constraint
|
|
|
|
|
|
|
| |
- note about unicode
- dont need importlater
- use correct type_ kw arg
- log cols/tables/etc as we autogenerate
|
|
|
|
|
|
|
| |
- add known status to CHANGES
- google group
- sa. prefix on modify type in autogenerate
- rename_table
|
| |
|
| |
|