./databases/py-alembic, Database migration tool for SQLAlchemy

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.9.6, Package name: py27-alembic-0.9.6, Maintainer: kamelderouiche

Alembic is a database migrations tool written by the author of
SQLAlchemy. A migrations tool can emit ALTER statements to a database
in order to change the structure of tables and other constructs,
provides a system whereby "migration scripts" may be constructed; each
script indicates a particular series of steps that can "upgrade" a
target database to a new version, and optionally a series of steps
that can "downgrade" similarly, doing the same steps in reverse, and
allows the scripts to execute in some sequential manner.


Required to run:
[time/py-dateutil]

Master sites:

SHA1: be22df78c2c9d49ebd0c6b7451eb6ca78dc12098
RMD160: d7fbde395cb025d37ca1f4e9275c53f42206de83
Filesize: 974.796 KB

Version history: (Expand)


CVS history: (Expand)


   2017-10-18 18:29:01 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-alembic: update to 0.9.6

0.9.6

feature

[feature] [commands] The alembic history command will now make use of the \ 
revision environment env.py unconditionally if the revision_environment \ 
configuration flag is set to True. Previously, the environment would only be \ 
invoked if the history specification were against a database-stored revision \ 
token.

bug

[bug] [commands] Fixed a few Python3.6 deprecation warnings by replacing \ 
StopIteration with return, as well as using getfullargspec() instead of \ 
getargspec() under Python 3.

[bug] [commands] An addition to 441 fixed in 0.9.5, we forgot to also filter for \ 
the + sign in migration names which also breaks due to the relative migrations \ 
feature.

[bug] [autogenerate] Fixed bug expanding upon the fix for 85 which adds the \ 
correct module import to the “inner” type for an ARRAY type, the fix now \ 
accommodates for the generic sqlalchemy.types.ARRAY type added in SQLAlchemy \ 
1.1, rendering the inner type correctly regardless of whether or not the \ 
Postgresql dialect is present.

[bug] [mysql] Fixed bug where server default comparison of CURRENT_TIMESTAMP \ 
would fail on MariaDB 10.2 due to a change in how the function is represented by \ 
the database during reflection.

[bug] [autogenerate] Fixed bug where comparison of Numeric types would produce a \ 
difference if the Python-side Numeric inadvertently specified a non-None \ 
“scale” with a “precision” of None, even though this Numeric type will \ 
pass over the “scale” argument when rendering. Pull request courtesy Ivan \ 
Mmelnychuk.

[bug] [batch] The name of the temporary table in batch mode is now generated off \ 
of the original table name itself, to avoid conflicts for the unusual case of \ 
multiple batch operations running against the same database schema at the same \ 
time.

[bug] [autogenerate] A ForeignKeyConstraint can now render correctly if the \ 
link_to_name flag is set, as it will not attempt to resolve the name from a \ 
“key” in this case. Additionally, the constraint will render as-is even if \ 
the remote column name isn’t present on the referenced remote table.

[bug] [runtime] [py3k] Reworked “sourceless” system to be fully capable of \ 
handling any combination of: Python2/3x, pep3149 or not, PYTHONOPTIMIZE or not, \ 
for locating and loading both env.py files as well as versioning files. This \ 
includes: locating files inside of __pycache__ as well as listing out version \ 
files that might be only in versions/__pycache__, deduplicating version files \ 
that may be in versions/__pycache__ and versions/ at the same time, correctly \ 
looking for .pyc or .pyo files based on if pep488 is present or not. The latest \ 
Python3x deprecation warnings involving importlib are also corrected.
   2017-09-17 06:00:15 by Min Sik Kim | Files touched by this commit (4) | Package updated
Log message:
databases/py-alembic: Import version 0.9.5 from pkgsrc-wip

Alembic is a database migrations tool written by the author of
SQLAlchemy. A migrations tool can emit ALTER statements to a database
in order to change the structure of tables and other constructs,
provides a system whereby "migration scripts" may be constructed; each
script indicates a particular series of steps that can "upgrade" a
target database to a new version, and optionally a series of steps
that can "downgrade" similarly, doing the same steps in reverse, and
allows the scripts to execute in some sequential manner.

Packaged by Kamel Ibn Aziz Derouiche and updated by me.