From 4c3d42ed758342eebbd34b32ae4cfdb8550fa396 Mon Sep 17 00:00:00 2001 From: iElectric Date: Sun, 28 Jun 2009 16:42:23 +0000 Subject: update changelog internal links --- docs/changelog.rst | 20 ++++++++++---------- docs/index.rst | 1 + 2 files changed, 11 insertions(+), 10 deletions(-) diff --git a/docs/changelog.rst b/docs/changelog.rst index f53c779..58e6ec3 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -4,24 +4,24 @@ - alter, create, drop column / rename table / rename index constructs now accept `alter_metadata` parameter. If True, it will modify Column/Table objects according to changes. Otherwise, everything will be untouched. - complete refactoring of :class:`~migrate.changeset.schema.ColumnDelta` (fixes issue 23) - added support for :ref:`firebird ` -- fixed bug when column.alter(server_default='string') was not properly set -- server_defaults passed to column.create are now issued correctly -- constraints passed to column.create are correctly interpreted (ALTER TABLE ADD CONSTRAINT is issued after ADD COLUMN) -- column.create accepts `primary_key_name`, `unique_name` and `index_name` as string value which is used as contraint name when adding a column -- Constraint classes have cascade=True keyword argument to issue CASCADE drop where supported -- added UniqueConstraint/CheckConstraint and corresponding create/drop methods +- fixed bug when :meth:`Column.alter `\(server_default='string') was not properly set +- `server_defaults` passed to :meth:`Column.create ` are now issued correctly +- constraints passed to :meth:`Column.create ` are correctly interpreted (``ALTER TABLE ADD CONSTRAINT`` is issued after ``ATLER TABLE ADD COLUMN``) +- :meth:`Column.create ` accepts `primary_key_name`, `unique_name` and `index_name` as string value which is used as contraint name when adding a column +- Constraint classes have `cascade=True` keyword argument to issue ``DROP CASCADE`` where supported +- added :class:`~migrate.changeset.constraint.UniqueConstraint`/:class:`~migrate.changeset.constraint.CheckConstraint` and corresponding create/drop methods - use SQLAlchemy quoting system to avoid name conflicts (for issue 32) - code coverage is up to 99% with more than 100 tests -- partial refactoring of changeset package +- partial refactoring of :mod:`changeset` package - majoy update to documentation -- dialect support table was added to documentation +- :ref:`dialect support ` table was added to documentation .. _backwards-055: **Backward incompatible changes**: -- python upgrade/downgrade scripts do not import migrate_engine magically, but recieve engine as the only parameter to function -- alter column does not accept `current_name` anymore, it extracts name from the old column. +- python upgrade/downgrade scripts do not import `migrate_engine` magically, but recieve engine as the only parameter to function (eg. ``def upgrade(migrate_engine):``) +- :meth:`Column.alter ` does not accept `current_name` anymore, it extracts name from the old column. 0.5.4 ----- diff --git a/docs/index.rst b/docs/index.rst index e3c471d..feb869c 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -39,6 +39,7 @@ Download and Development download +.. _dialect-support: Dialect support --------------- -- cgit v1.2.1