Changelog for python-alembic-0.5.0-2.1.noarch.rpm :

* Sun Apr 14 2013 p.drouandAATTgmail.com- Update to version 0.5.0 + added version_table_schema argument to EnvironmentContext.configure(), complements the version_table argument to set an optional remote schema for the version table. + added output_encoding option to EnvironmentContext.configure(), used with --sql mode to apply an encoding to the output stream. + added Operations.create_primary_key() operation, will genenerate an ADD CONSTRAINT for a primary key. + upgrade and downgrade commands will list the first line of the docstring out next to the version number. + added –head-only option to “alembic current”, will print current version plus the symbol “(head)” if this version is the head or not. + the rendering of any construct during autogenerate can be customized, in particular to allow special rendering for user-defined column, constraint subclasses, using new render _item argument to EnvironmentContext.configure(). + fix format of RENAME for table that includes schema with Postgresql; the schema name shouldn’t be in the “TO” field. + fix bug whereby double quoting would be applied to target column name during an sp_rename operation. + fix transactional_ddl flag for SQLite, MySQL dialects set to False. MySQL doesn’t support it, SQLite does but current pysqlite driver does not. + fix Autogenerate will render additional table keyword arguments like “mysql_engine” and others within op.create_table(). + fix bug whereby create_index() would include in the constraint columns that are added to all Table objects using events, externally to the generation of the constraint. This is the same issue that was fixed for unique constraints in version 0.3.2. + fix worked around a backwards-incompatible regression in Python3.3 regarding argparse; running “alembic” with no arguments now yields an informative error in py3.3 as with all previous versions. + fix host of argument name changes within migration operations for consistency. Keyword arguments will continue to work on the old name for backwards compatibility, however required positional arguments will not:
* Operations.alter_column() - name -> new_column_name - old name will work for backwards compatibility.
* Operations.create_index() - tablename -> table_name - argument is positional.
* Operations.drop_index() - tablename -> table_name - old name will work for backwards compatibility.
* Operations.drop_constraint() - tablename -> table_name - argument is positional.
* Operations.drop_constraint() - type -> type_ - old name will work for backwards compatibility + SQLAlchemy 0.6 is no longer supported by Alembic - minimum version is 0.7.3, full support is as of 0.7.9.- Initial python3 support
* Thu Jan 17 2013 toddrme2178AATTgmail.com- Set nose version requirement
* Mon Jan 14 2013 saschpeAATTsuse.de- Update to version 0.4.2: + Fixed bug where autogenerate would fail if a Column to be added to a table made use of the \".key\" paramter. + Added a workaround to setup.py to prevent \"NoneType\" error from occuring when \"setup.py test\" is run. + Added a README.unittests with instructions for running the test suite fully.- Changes from version 0.4.1: + Added support for autogenerate render of ForeignKeyConstraint options onupdate, ondelete, initially, and deferred. + Explicit error message describing the case when downgrade --sql is used without specifying specific start/end versions. + Fixed the minute component in file_template which returned the month part of the create date.
* Mon Jan 14 2013 saschpeAATTsuse.de- Disable testsuite on SLE
* Fri Nov 23 2012 saschpeAATTsuse.de- Update to version 0.4.0: + [feature] Support for tables in alternate schemas 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. + [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 + [feature] Added \"stdout\" option to Config, provides control over where the \"print\" output of commands like \"history\", \"init\", \"current\" etc. are sent. #43 + [bug] Fixed the \"multidb\" template which was badly out of date. It now generates revision files using the configuration to determine the different upgrade_() methods needed as well, instead of needing to hardcode these. Huge thanks to BryceLohr for doing the heavy lifting here. #71 + [bug] Fixed the regexp that was checking for .py files 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 + [bug] Fixed MySQL rendering for server_default which didn\'t work if the server_default was a generated SQL expression. Courtesy Moriyoshi Koizumi. + [feature] Added support for alteration of MySQL columns that have AUTO_INCREMENT, as well as enabling this flag. Courtesy Moriyoshi Koizumi.
* Wed Jun 06 2012 saschpeAATTsuse.de- Update to version 0.3.4: + [bug] Fixed command-line bug introduced by the \"revision_environment\" feature.- Changes from version 0.3.3: + [feature] New config argument \"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\". + [bug] Added \"type\" argument to op.drop_constraint(), 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 version_table argument to EnvironmentContext.configure(), allowing for the configuration of the version table name. #34 + [feature] Added support for \"relative\" migration identifiers, i.e. \"alembic upgrade +2\", \"alembic downgrade -1\". Courtesy Atsushi Odagiri for this feature. + [bug] Fixed bug whereby directories inside of the template directories, such as __pycache__ on Pypy, would mistakenly be interpreted as files which are part of the template. #49
* Wed May 23 2012 saschpeAATTsuse.de- Update to version 0.3.2: + [feature] Basic support for Oracle added + [feature] Added support for UniqueConstraint in autogenerate + [bug] Fixed support of schema-qualified ForeignKey target in column alter operations, + [bug] Fixed bug whereby create_unique_constraint() would include in the constraint columns that are added to all Table objects using events, externally to the generation of the constraint.- Changes from version 0.3.1: + [bug] bulk_insert() fixes: 1. bulk_insert() operation was not working most likely since the 0.2 series when used with an engine 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.- Changes from version 0.3.0: + [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.
* Wed Mar 07 2012 saschpeAATTsuse.de- Initial version