| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Alembic is now under the sqlalchemy.org domain
for the website and all repos are moving under github.com/sqlalchemy.
Change-Id: Id9ce08b61ed0ccdf50396f911838b21112e61652
|
| | |
|
| | |
|
| |
|
|
| |
correctly
|
| |
|
|
|
| |
from operations.create_table() documentation.
#81
|
| |
|
|
|
| |
when downgrade --sql is used without specifying
specific start/end versions. #66
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
control over where the "print" output of commands like
"history", "init", "current" etc. are sent. #43
|
| |
|
|
|
|
|
|
| |
of date. It now generates revision files using
the configuration to determine the different
upgrade_<xyz>() methods needed as well, instead of
needing to hardcode these. Huge thanks to
BryceLohr for doing the heavy lifting here. #71
|
| |
|
|
|
|
|
|
| |
in the version directory to allow any .py file through.
Previously it was doing some kind of defensive checking,
probably from some early notions of how this directory
works, that was prohibiting various filename patterns
such as those which begin with numbers. #72
|
| |
|
|
|
|
|
| |
- [feature] The command line runner has been organized
into a reusable CommandLine object, so that other
front-ends can re-use the argument parsing built
in. #70
|
| | |
|
| |
|
|
|
| |
didn't work if the server_default was a generated
SQL expression. Courtesy Moriyoshi Koizumi.
|
| |
|
|
|
|
|
| |
EnvironmentContext.configure(),
specifies a callable which will include/exclude tables
in their entirety from the autogeneration process
based on name. #27
|
| |
|
|
|
|
| |
non-ordered revision identifiers to cover
the case when the "higher" rev is None,
improved message overall. #66
|
| |
|
|
|
| |
self-referential foreign keys, which weren't working
at all.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
alongside so-called "schema" types such as
Boolean and Enum. The create/drop constraint logic
does not kick in when using a dialect that doesn't
use constraints for these types, such as postgresql,
even when existing_type is specified to
alter_column(). Additionally, the constraints
are not affected if existing_type is passed but
type_ is not, i.e. there's no net change
in type. #62
|
| |
|
|
|
| |
error message when the configuration is missing
the 'script_directory' key. #63
|
| |
|
|
|
|
| |
for the use case where the "revision_environment"
config option is being used but SQL access isn't
desired.
|
| |
|
|
|
|
| |
- changelog
- fix this test
- fix docs for new mysql 'primary'
|
| |
|
|
| |
variables to file_template. #59
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
- its beta
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
"revision_environment=true", causes env.py to
be run unconditionally when the "revision" command
is run, to support script.py.mako templates with
dependencies on custom "template_args".
- [feature] Added "template_args" option to configure()
so that an env.py can add additional arguments
to the template context when running the
"revision" command. This requires either --autogenerate
or the configuration directive "revision_environment=true".
|
| |
|
|
|
|
| |
the template directories, such as __pycache__
on Pypy, would mistakenly be interpreted as
files which are part of the template. #49
|
| |
|
|
|
|
| |
identifiers, i.e. "alembic upgrade +2",
"alembic downgrade -1". Courtesy
Atsushi Odagiri for this feature.
|
| | |
|
| |
|
|
|
|
|
| |
and implemented full constraint drop support for
MySQL. CHECK and undefined raise an error.
MySQL needs the constraint type
in order to emit a DROP CONSTRAINT. #44
|
| |
|
|
| |
courtesy shgoh. #40
|
| |
|
|
|
|
| |
would include in the constraint columns that
are added to all Table objects using events,
externally to the generation of the constraint.
|
| |
|
|
|
| |
ForeignKey target in column alter operations,
courtesy Alexander Kolov.
|
| |
|
|
| |
in autogenerate, courtesy Atsushi Odagiri
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. bulk_insert() operation was
not working most likely since the 0.2 series
when used with an engine. #41
2. Repaired bulk_insert() to complete when
used against a lower-case-t table and executing
with only one set of parameters, working
around SQLAlchemy bug #2461 in this regard.
3. bulk_insert() uses "inline=True" so that phrases
like RETURNING and such don't get invoked for
single-row bulk inserts.
4. bulk_insert() will check that you're passing
a list of dictionaries in, raises TypeError
if not detected.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- [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.
|
| |
|
|
| |
- import OrderedSet from sqlalchemy.util
|
| |
|
|
|
|
|
| |
util.err() and therefore sys.exit()
when Config failed to locate the
config file within library usage.
[#35]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
drop_index() as this is needed by some
backends.
- [feature] Added execution_options parameter
to op.execute(), will call execution_options()
on the Connection before executing.
The immediate use case here is to allow
access to the new no_parameters option
in SQLAlchemy 0.7.6, which allows
some DBAPIs (psycopg2, MySQLdb) to allow
percent signs straight through without
escaping, thus providing cross-compatible
operation with DBAPI execution and
static script generation.
|
| |
|
|
| |
directives are invoked at module import time.
|
| |
|
|
|
| |
is added when it calls "Index", as SQLAlchemy
0.7.6 will warn on index with no column names.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
by pkg_resources.resource_filename(), if
it is a non-absolute URI that contains
colons. This scheme is the same
one used by Pyramid. [#29]
|
| | |
|
| |
|
|
| |
regression from 0.2.0 [#26]
|
| | |
|
| |
|
|
|
|
|
|
| |
connection.close() to better support
programmatic usage of commands; use
NullPool in conjunction with create_engine()
as well so that no connection resources
remain afterwards. [#25]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
variables to get to things. The new structure is:
EnvironmentContext -> MigrationContext -> Operation
EnvironmentContext sets up the variables "alembic.context"
and "alembic.op" to act like the modules they used to.
MigrationContext can also exist independently of EnvironmentContext.
Refactoring is still underway here.
|
| |
|
|
|
|
| |
with no filename, use set_main_option()
to add values. Also added set_section_option()
which will add sections. [#23]
|
