[gerrit]
host=gerrit.sqlalchemy.org
-project=zzzeek/alembic
+project=sqlalchemy/alembic
defaultbranch=master
port=29418
or
- http://alembic.zzzcomputing.com/en/latest/changelog.html
+ http://alembic.sqlalchemy.org/en/latest/changelog.html
for the current CHANGES.
other databases, if you want to recreate a table in the background
on a busy system.
-Documentation and status of Alembic is at http://alembic.zzzcomputing.com/
+Documentation and status of Alembic is at https://alembic.sqlalchemy.org/
is the same length as the .expressions collection. Ultimately
SQLAlchemy should support text() expressions in indexes.
- See https://bitbucket.org/zzzeek/sqlalchemy/issue/3174/\
- support-text-sent-to-indexes
+ See SQLAlchemy issue 3174.
"""
__visit_name__ = '_textual_idx_element'
.. change::
:tags: bug, autogenerate
- :pullreq: bitbucket:70
Fixed bug where comparison of ``Numeric`` types would produce
a difference if the Python-side ``Numeric`` inadvertently specified
.. change::
:tags: bug, batch
:tickets: 361
- :pullreq: bitbucket:55
Fixed bug introduced by the fix for :ticket:`338` in version 0.8.4
where a server default could no longer be dropped in batch mode.
.. change::
:tags: bug, batch, mssql
- :pullreq: bitbucket:53
Fixed bug where SQL Server arguments for drop_column() would not
be propagated when running under a batch block. Pull request
.. change::
:tags: bug, autogenerate
:tickets: 335
- :pullreq: bitbucket:49
Fixed bug where the columns rendered in a ``PrimaryKeyConstraint``
in autogenerate would inappropriately render the "key" of the
.. change::
:tags: feature, versioning
- :pullreq: bitbucket:51
A major improvement to the hash id generation function, which for some
reason used an awkward arithmetic formula against uuid4() that produced
.. change::
:tags: feature, autogenerate
- :pullreq: github:20
Added an autogenerate renderer for the :class:`.ExecuteSQLOp` operation
object; only renders if given a plain SQL string, otherwise raises
.. change::
:tags: bug, tests
- :pullreq: bitbucket:47
Added "pytest-xdist" as a tox dependency, so that the -n flag
in the test command works if this is not already installed.
.. change::
:tags: feature, commands
- :pullreq: bitbucket:46
Added new command ``alembic edit``. This command takes the same
arguments as ``alembic show``, however runs the target script
.. change::
:tags: bug, autogenerate
:tickets: 266
- :pullreq: bitbucket:39
The ``--autogenerate`` option is not valid when used in conjunction
with "offline" mode, e.g. ``--sql``. This now raises a ``CommandError``,
.. change::
:tags: bug, autogenerate, postgresql
:tickets: 241
- :pullreq: bitbucket:37
Repaired issue where a server default specified without ``text()``
that represented a numeric or floating point (e.g. with decimal places)
.. change::
:tags: bug, autogenerate
:tickets: 261
- :pullreq: github:17
Fixed issue in autogenerate type rendering where types that belong
to modules that have the name "sqlalchemy" in them would be mistaken
.. change::
:tags: bug, mysql
:tickets: 251
- :pullreq: bitbucket:35
Fixed an issue where the MySQL routine to skip foreign-key-implicit
indexes would also catch unnamed unique indexes, as they would be
.. change::
:tags: feature, autogenerate
:tickets: 178
- :pullreq: bitbucket:32
Support for autogenerate of FOREIGN KEY constraints has been added.
These are delivered within the autogenerate process in the same
.. change::
:tags: bug, batch
- :pullreq: bitbucket:34
Fixed bug where the "source_schema" argument was not correctly passed
when calling :meth:`.BatchOperations.create_foreign_key`. Pull
.. change::
:tags: feature, config
- :pullreq: bitbucket:33
Added new argument :paramref:`.Config.config_args`, allows a dictionary
of replacement variables to be passed which will serve as substitution
.. change::
:tags: bug, operations
:tickets: 174
- :pullreq: bitbucket:29
The :meth:`.Operations.add_column` directive will now additionally emit
the appropriate ``CREATE INDEX`` statement if the
.. change::
:tags: bug, mssql
- :pullreq: bitbucket:26
Fixed bug in MSSQL dialect where "rename table" wasn't using
``sp_rename()`` as is required on SQL Server. Pull request courtesy
.. change::
:tags: bug
:tickets: 95
- :pullreq: bitbucket:24
A file named ``__init__.py`` in the ``versions/`` directory is now
ignored by Alembic when the collection of version files is retrieved.
.. change::
:tags: bug
- :pullreq: bitbucket:23
Fixed Py3K bug where an attempt would be made to sort None against
string values when autogenerate would detect tables across multiple
.. change::
:tags: bug
- :pullreq: github:15
Autogenerate render will render the arguments within a Table construct
using ``*[...]`` when the number of columns/elements is greater than
.. change::
:tags: bug
- :pullreq: github:14
Fixed bug where foreign key constraints would fail to render in
autogenerate when a schema name was present. Pull request courtesy
.. change::
:tags: feature
- :pullreq: github:10
Added a new accessor :attr:`.MigrationContext.config`, when used
in conjunction with a :class:`.EnvironmentContext` and
.. change::
:tags: feature
- :pullreq: bitbucket:20
The :func:`.command.revision` command now returns the :class:`.Script`
object corresponding to the newly generated revision. From this
.. change::
:tags: bug
- :pullreq: github:9
The :func:`.compare_metadata` public API function now takes into
account the settings for
.. change::
:tags: bug
- :pullreq: bitbucket:17
Enabled schema support for index and unique constraint autodetection;
previously these were non-functional and could in some cases lead to
.. change::
:tags: bug, mssql
- :pullreq: bitbucket:13
The MSSQL backend will add the batch separator (e.g. ``"GO"``)
in ``--sql`` mode after the final ``COMMIT`` statement, to ensure
.. change::
:tags: feature
- :pullreq: bitbucket:12
Expanded the size of the "slug" generated by "revision" to 40
characters, which is also configurable by new field
.. change::
:tags: bug
- :pullreq: bitbucket:9
Fixes to Py3k in-place compatibity regarding output encoding and related;
the use of the new io.* package introduced some incompatibilities on Py2k.
The author asks that you *please* report all
issues, missing features, workarounds etc.
- to the bugtracker, at
- https://bitbucket.org/zzzeek/alembic/issues/new .
+ to the bugtracker.
.. change::
:tags:
# tags to sort on inside of sections
changelog_sections = ["changed", "feature", "bug", "moved", "removed"]
-changelog_render_ticket = "https://bitbucket.org/zzzeek/alembic/issue/%s/"
-changelog_render_pullreq = "https://bitbucket.org/zzzeek/alembic/pull-request/%s"
+changelog_render_ticket = "https://github.com/sqlalchemy/alembic/issues/%s"
+changelog_render_pullreq = "https://github.com/sqlalchemy/alembic/pull/%s"
changelog_render_pullreq = {
- "bitbucket": "https://bitbucket.org/zzzeek/alembic/pull-request/%s",
- "default": "https://bitbucket.org/zzzeek/alembic/pull-request/%s",
- "github": "https://github.com/zzzeek/alembic/pull/%s",
+ "default": "https://github.com/sqlalchemy/alembic/pull/%s",
+ "github": "https://github.com/sqlalchemy/alembic/pull/%s",
}
autodoc_default_flags = ["members"]
We first need to devise a simple format that represents the "CREATE XYZ" /
"DROP XYZ" aspect of what it is we're building. We will work with an object
that represents a textual definition; while a SQL view is an object that we can define
-using a `table-metadata-like system <https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/Views>`_,
+using a `table-metadata-like system <https://github.com/sqlalchemy/sqlalchemy/wiki/UsageRecipes/Views>`_,
this is not so much the case for things like stored procedures, where
we pretty much need to have a full string definition written down somewhere.
We'll use a simple value object called ``ReplaceableObject`` that can
Project Homepage
================
-Alembic is hosted on `Bitbucket <http://bitbucket.org>`_ - the lead project
-page is at https://bitbucket.org/zzzeek/alembic. Source code is tracked here
-using `Git <http://git-scm.com/>`_.
+Alembic is hosted on GitHub at https://github.com/sqlalchemy/alembic under the SQLAlchemy organization.
-Releases and project status are available on Pypi at
-http://pypi.python.org/pypi/alembic.
+Releases and project status are available on Pypi at https://pypi.python.org/pypi/alembic.
+
+The most recent published version of this documentation should be at https://alembic.sqlalchemy.org.
-The most recent published version of this documentation should be at
-http://alembic.sqlalchemy.org/.
.. _installation:
Bugs
====
-Bugs and feature enhancements to Alembic should be reported on the `Bitbucket
-issue tracker <https://bitbucket.org/zzzeek/alembic/issues?status=new&status=open>`_.
+Bugs and feature enhancements to dogpile.cache should be reported on the `GitHub
+issue tracker
+<https://github.com/sqlalchemy/alembic/issues/>`_.
-.. _SQLAlchemy: http://www.sqlalchemy.org
+.. _SQLAlchemy: https://www.sqlalchemy.org
Welcome to Alembic's documentation!
===================================
-`Alembic <http://bitbucket.org/zzzeek/alembic>`_ is a lightweight database migration tool for usage
-with the `SQLAlchemy <http://www.sqlalchemy.org>`_ Database Toolkit for Python.
+`Alembic <https://alembic.sqlalchemy.org>`_ is a lightweight database migration tool for usage
+with the `SQLAlchemy <https://www.sqlalchemy.org>`_ Database Toolkit for Python.
.. toctree::
:maxdepth: 3
git+https://bitbucket.org/zzzeek/changelog.git#egg=changelog
git+https://bitbucket.org/zzzeek/sphinx-paramlinks.git#egg=sphinx-paramlinks
-git+https://bitbucket.org/zzzeek/sqlalchemy.git
+git+https://github.com/sqlalchemy/sqlalchemy.git
python-dateutil
Tutorial
========
-`Alembic <http://bitbucket.org/zzzeek/alembic>`_ provides for the creation, management, and invocation of *change management*
-scripts for a relational database, using `SQLAlchemy <http://www.sqlalchemy.org>`_ as the underlying engine.
+Alembic provides for the creation, management, and invocation of *change management*
+scripts for a relational database, using SQLAlchemy as the underlying engine.
This tutorial will provide a full introduction to the theory and usage of this tool.
To begin, make sure Alembic is installed as described at :ref:`installation`.
--- /dev/null
+.. change::
+ :tags: change
+
+ Code hosting has been moved to GitHub, at
+ https://github.com/sqlalchemy/alembic. Additionally, the
+ main Alembic website documentation URL is now
+ https://alembic.sqlalchemy.org.
keywords='SQLAlchemy migrations',
author='Mike Bayer',
author_email='mike@zzzcomputing.com',
- url='http://bitbucket.org/zzzeek/alembic',
+ url='https://alembic.sqlalchemy.org',
license='MIT',
packages=find_packages('.', exclude=['examples*', 'test*']),
include_package_data=True,
# old unicode statements flag
envlist = py{27,34,35,36,37}-sqla{10,11,12,master}, py{27}-sqla{079,084,09}
-SQLA_REPO = {env:SQLA_REPO:git+https://zzzeek@bitbucket.org/zzzeek/sqlalchemy.git}
+SQLA_REPO = {env:SQLA_REPO:git+https://github.com/sqlalchemy/sqlalchemy.git}
[testenv]
cov_args=--cov=alembic --cov-report term --cov-report xml
projects / thirdparty / sqlalchemy / alembic.git / commitdiff
