| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
like to run tests against 0.8 and even late 0.7 versions with the same
capabilities, as well as run parallel testing against all of them.
we need a consistent system to get that all to work, so for now
we have the whole SQLA system shoved into here, not ideal but we have
a very good testing situation for now. Once we target 0.9.4 at the lowest
we should be able to move all this out.
- re-support 0.7, starting at 0.7.6 which is where things mostly work.
All tests, taking into account known skips and fails which are
added here for 0.7, early 0.8s, pass on 0.7.9.
|
| | |
|
| | |
|
| |
|
|
| |
than line length
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
| |
:meth:`.Operations.drop_column`. Like ``mssql_drop_default``
and ``mssql_drop_check``, will do an inline lookup for a
single foreign key which applies to this column, and drop it.
For a column with more than one FK, you'd still need to explicitly
use :meth:`.Operations.drop_constraint` given the name,
even though only MSSQL has this limitation in the first place.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- cleanup unused symbols in compat
- move any remaining conditional import switches out to compat
- pretty sure anything we use for a buffer will have flush()
- I can see that using the new io.* stuff means codecs isn't too
smooth here, but removed the double-wrap check in migration.py
which seems to be due to the bytesio setup in the test suite, simplified
this so that an encoding-writing test just writes to BytesIO
- removed all "from __future__ import with_statement"
- i think when we load_source(), that file might not be ascii
so we need to open as bytes
- make encoding an explcit argument in test suite write_script()
- sort the columns in autogenerate so that the autogen tests run
consistently on python3.3, seems to have a very random set ordering,
also loosen up an ordered check in test_op
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
to target column name during an ``sp_rename``
operation.
#109
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- add a generalized approach for renamed kw args, accepting the old
ones using a specialized decorator
- change "tablename" to "table_name" for create_index, drop_index,
drop_constraint
- change "name" to "new_column_name" for alter_column
#104
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
MSSQL to not include the keyword "TYPE".
|
| |
|
|
| |
__future__.with_statement
|
| |
|
|
|
|
| |
file handles are closed.
- PyPy is supported.
|
| | |
|
| |
|
|
| |
- i want the ; after BEGIN/COMMIT for static generation, makes it easier to parse
|
| | |
|
| |
|
|
| |
- implement SQL server alter column rules regarding NULL/NOT NULL
|
| |
|
|
|
|
| |
- implement counter logic for SQL server constraint/default
drop so that variables are declared uniquely within
a full migration run, #12
|
| |
|
|
|
|
|
|
|
| |
begin/commit pair regardless of context.
- add dialect support for BEGIN/COMMIT working corresponding
to backend. Add implementation for SQL server.
- add tests for BEGIN/COMMIT , #11
- rework SQL server test suite for more classes of test
- fix test suite to clean up after a prior failed suite
|
| |
|
|
|
| |
- add support for actual DB connections, test.cfg, etc.
- add PG server default comparison tests, #6
|
| |
|
|
| |
NULL to SQL Server, until we get more data on other DBs
|
| |
|
|
|
|
|
| |
rule
- add mssql_drop_default, mssql_drop_check flags to drop_column(),
will emit special MSSQL crap to drop DEFAULT and CHECK constraints based
on inline system table lookup
|
| | |
|
|
|
mediates at a high level, into ddl/impl, which deals with DB stuff
- fix MSSQL add column, #2
|
