summaryrefslogtreecommitdiff
path: root/alembic/__init__.py
Commit message (Collapse)AuthorAgeFilesLines
* 0.7 startMike Bayer2014-09-131-1/+1
|
* 0.6.7rel_0_6_7rel_0_6Mike Bayer2014-09-091-1/+1
|
* - do an autopep8 pass for just about everything otherMike Bayer2014-09-091-2/+0
| | | | than line length
* this is 0.6.6Mike Bayer2014-06-241-1/+1
|
* Fixed another bug regarding naming conventions, continuingMike Bayer2014-04-011-1/+1
| | | | | | | 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
* - 0.6.4Mike Bayer2014-02-171-1/+1
| | | | - changelog for pullreq bitbucket:20
* - The :class:`.ScriptDirectory` system that loads migration filesMike Bayer2013-12-311-1/+1
| | | | | | | | | | | | | from a ``versions/`` directory now supports so-called "sourceless" operation, where the ``.py`` files are not present and instead ``.pyc`` or ``.pyo`` files are directly present where the ``.py`` files should be. Note that while Python 3.3 has a new system of locating ``.pyc``/``.pyo`` files within a directory called ``__pycache__`` (e.g. PEP-3147), PEP-3147 maintains support for the "source-less imports" use case, where the ``.pyc``/``.pyo`` are in present in the "old" location, e.g. next to the ``.py`` file; this is the usage that's supported even when running Python3.3. #163
* - 0.6.2Mike Bayer2013-12-051-1/+1
| | | | - changelog for pullreq 13
* - refactor autogeneration into its own packageMike Bayer2013-09-081-0/+1
| | | | | | | - remove any implicit naming of unique constraints - only explcitly named constraints are supported by autogenerate - ensure we correctly handle the case where unique reflection raises not implemented - fix some naming conventions, changes to expressions for readability
* - Ensured that strings going to stdout go through an encode/decode phase,Mike Bayer2013-08-231-1/+1
| | | | | | | so that any non-ASCII characters get to the output stream correctly in both Py2k and Py3k. Also added source encoding detection using Mako's parse_encoding() routine in Py2k so that the __doc__ of a non-ascii revision file can be treated as unicode in Py2k.
* - will call this 0.6Mike Bayer2013-04-121-1/+1
| | | | | | | | | | | | | | | | | - 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
* Use relative importsHong Minhee2013-04-111-2/+2
| | | | | | | | | | | | | | | | | | | | | 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.
* - move to 0.5.0 as we are making some slight naming changesMike Bayer2013-02-111-1/+1
| | | | | | | | | - 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
* ok seems we're up to 0.4.3...Mike Bayer2013-02-041-1/+1
|
* 0.4.2rel_0_4_2Mike Bayer2013-01-111-1/+1
|
* - [feature] Explicit error message describing the caseMike Bayer2012-10-181-1/+1
| | | | | when downgrade --sql is used without specifying specific start/end versions. #66
* - call it 0.4.0Mike Bayer2012-09-301-1/+1
| | | | | | | - [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
* - [bug] Fixed MySQL rendering for server_default whichMike Bayer2012-08-221-1/+1
| | | | | didn't work if the server_default was a generated SQL expression. Courtesy Moriyoshi Koizumi.
* - [feature] Added --sql argument to the "revision" command,Mike Bayer2012-07-281-1/+1
| | | | | | for the use case where the "revision_environment" config option is being used but SQL access isn't desired.
* - apply repr() to server default string, #31Mike Bayer2012-06-231-1/+1
|
* - repair entirely broken revision_environment feature released in 0.3.3rel_0_3_4Mike Bayer2012-06-021-1/+1
| | | | - its beta
* - [bug] Added "type" argument to op.drop_constraint(),Mike Bayer2012-05-011-1/+1
| | | | | | | 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
* - [feature] Added support for UniqueConstraintMike Bayer2012-04-211-1/+1
| | | | in autogenerate, courtesy Atsushi Odagiri
* - [bug] bulk_insert() fixes:rel_0_3_1Mike Bayer2012-04-071-1/+1
| | | | | | | | | | | | | | | | 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.
* - move to 0.3 as we are changing APIrel_0_3_0Mike Bayer2012-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | - [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.
* - update version + CHANGES for rff49b7fe01b4Mike Bayer2012-02-031-1/+1
|
* - [bug] Fixed the generation of CHECK constraint,Mike Bayer2012-01-311-1/+1
| | | | regression from 0.2.0 [#26]
* turn alembic.op and alembic.context into real proxy modules,Mike Bayer2012-01-261-6/+1
| | | | | with an accurate system of reflecting the Operations and EnvironmentContext methods into them.
* - tried it out in my work project, and realized the "op" and "context" ↵Mike Bayer2012-01-241-4/+7
| | | | | | | | | | namespaces need to be there fully and in particular "context" needs to be a proxy object, as env.py may have dependencies which live beyond the scope of the migration script. Will have to try to make these proxies as straightforward as possible. - more architecture docs
* - rearrange the internals such that we no longer use globalMike Bayer2012-01-241-1/+7
| | | | | | | | | | | | 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.
* - [bug] fix the config.main() function to honorMike Bayer2012-01-201-1/+1
| | | | | | the arguments passed, remove no longer used "scripts/alembic" as setuptools creates this for us. [#22]
* - Clean up file write operations so thatMike Bayer2011-12-031-1/+1
| | | | | | file handles are closed. - PyPy is supported.
* - docsMike Bayer2011-11-271-1/+1
| | | | | | | - note about unicode - dont need importlater - use correct type_ kw arg - log cols/tables/etc as we autogenerate
* do "find the templates" identically to how sphinx does itMike Bayer2011-04-191-0/+2
|
* some ui improvementsMike Bayer2010-04-291-93/+0
|
* upgrade, downgrade motionMike Bayer2010-04-291-24/+41
|
* - pushed the whole command line options thing into a single main() functionMike Bayer2010-04-281-9/+71
| | | | | | | - command methods now accept a "config" plus positional + kw arguments, for easy API calling - main() provides context sensitive arguments and help for each command using inspect.getargspec()
* commandsMike Bayer2010-04-251-1/+15
|
* - figuring out script formatMike Bayer2010-04-241-1/+1
| | | | - figuring out operation system
* a sandwich setup.Mike Bayer2010-04-221-0/+4
View Lorry Controller Status