openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of python-alembic

buildservice-autocommit accepted request 1135249 from

Dirk Mueller (dirkmueller) 4 months ago (revision 159)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 4 months ago (revision 158)

- update to 1.13.1:
  * Fixed :class:`.Rewriter` so that more than two instances
    could be chained together correctly, also allowing multiple
    ``process_revision_directives`` callables to be chained.
  * Fixed issue where the method
    :meth:`.EnvironmentContext.get_x_argument` using the
    :paramref:`.EnvironmentContext.get_x_argument.as_dictionary`
    parameter would fail if an argument key were passed on the
    command line as a name alone, that is, without an equal sign
    ``=`` or a value. Behavior is repaired where this condition is
    detected and will return a blank string for the given key,
    consistent with the behavior where the ``=`` sign is
    present and no value.
  * Fixed issue where the "unique" flag of an ``Index`` would not
    be maintained when generating downgrade migrations.
  * Fixed bug in versioning model where a downgrade across a
    revision with two down revisions with one down revision
    depending on the other, would produce an erroneous state in
    the alembic_version table, making upgrades impossible
    without manually repairing the table.
  * Updated pep-484 typing to pass mypy "strict" mode, however
    including per-module qualifications for specific typing
    elements not yet complete.
  * This allows us to catch specific typing issues that have been
    ongoing such as import symbols not properly exported.

buildservice-autocommit accepted request 1133430 from

Dirk Mueller (dirkmueller) 5 months ago (revision 157)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 5 months ago (revision 156)

    function correctly with upgrade structures that have multiple,
    top-level elements, as are generated from the "multi-env"
    environment template.
    ``if_exists`` and ``if_not_exists`` on index operations also
    on SQLAlchemy  1.4 series. Previously this feature was
    mistakenly requiring the 2.0 series.
    zoneinfo.
    ``drop_table_comment()`` rendering in a batch table modify
    would include the "table" and "schema" arguments, which are
    not accepted in batch as these are already part of the top
    level block.
    feature. The compare now correctly accommodates casts and
    differences in spacing.
    expression, skipping the compare of these expressions.
    the indexes and unique constraints was moved to the dialect
    implementation, allowing greater flexibility.

Markéta Machová (mcalabkova) accepted request 1133130 from

Petr Gajdos (pgajdos) 5 months ago (revision 155)

pmmu version update

buildservice-autocommit accepted request 1125874 from

Dirk Mueller (dirkmueller) 6 months ago (revision 154)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 6 months ago (revision 153)

- update to 1.12.1:
  * Fixed regression caused by :ticket:`879` released in 1.7.0
    where the ".info" dictionary of ``Table`` would not render in
    autogenerate create table statements.
    This can be useful for custom create table DDL rendering
    schemes so it is restored.
  * Improved typing in the
    :paramref:`.EnvironmentContext.configure.process_revision_dir
    ectives` callable to better indicate that the passed-in type is
    :class:`.MigrationScript`, not the :class:`.MigrationOperation`
    base class, and added typing to the example at
    :ref:`cookbook_no_empty_migrations` to illustrate.
  * Repaired :class:`.ExecuteSQLOp` so that it can participate in
    "diff" operations; while this object is typically not present
    in a reflected operation stream, custom hooks may be adding
    this construct where it needs to have the correct
    ``to_diff_tuple()`` method.
  * Improved the ``op.execute()`` method to correctly accept the
  * ``Executable`` type that is the same which is used in
    SQLAlchemy ``Connection.execute()``.
  * Improve typing of the revision parameter in various command
    functions.
  * Fixed autogen render issue where expressions inside of
    indexes for PG need to be double-parenthesized, meaning a
    single parens must be present within the generated ``text()``
    construct.
  * Alembic now accommodates for Sequence and Identity that
    support dialect kwargs.
    This is a change that will be added to SQLAlchemy v2.1.
    not use semver, nor does its parent project SQLAlchemy;

buildservice-autocommit accepted request 1113553 from

Matej Cepl (mcepl) 7 months ago (revision 152)

baserev update by copy to link target

Matej Cepl (mcepl) committed 7 months ago (revision 151)

- Clean up the SPEC file

Matej Cepl (mcepl) accepted request 1113500 from

Ondřej Súkup (mimi_vx) 7 months ago (revision 150)

- update to 1.12.0
 * Added new feature to the "code formatter" function which allows standalone
   executable tools to be run against code, without going through the Python
   interpreter.  Known as the `exec` runner, it complements the existing
   `console_scripts` runner by allowing non-Python tools such as `ruff` to
   be used.
 * Change the default value of `.EnvironmentContext.configure.compare_type` to `True`.
   As Alembic's autogenerate for types was dramatically improved in
   version 1.4 released in 2020, the type comparison feature is now much
   more reliable so is now enabled by default.
 * Fixed issue where the `ForeignKeyConstraint.match` parameter would not be
   rendered in autogenerated migrations.
 * Fixed issue where the `revision_environment` directive in `alembic.ini`
   was ignored by the `alembic merge` command, leading to issues when other
   configurational elements depend upon `env.py` being invoked within the
   command.
 * Added support for `op.drop_constraint()` to support PostgreSQL
   `ExcludeConstraint` objects, as well as other constraint-like objects
   that may be present in third party dialects, by resolving the `type_`
   parameter to be `None` for this case.   Autogenerate has also been
   enhanced to exclude the `type_` parameter from rendering within this
   command when  `type_` is `None`.

buildservice-autocommit accepted request 1103719 from

Dirk Mueller (dirkmueller) 9 months ago (revision 149)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 9 months ago (revision 148)

- update to 1.11.2:
  * Added typing to the default script mako templates.
  * Added support in autogenerate for NULLS NOT DISTINCT in
  * the PostgreSQL dialect.
  * Fixed format string logged when running a post write hook
  * Added parameters if_exists and if_not_exists for index
    operations.

buildservice-autocommit accepted request 1102506 from

Factory Maintainer (factory-maintainer) 9 months ago (revision 147)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 9 months ago (revision 146)

- update to 1.11.1:
  * As Alembic 1.11.0 is considered a major release (Alembic does
    not use semver, nor does its parent project SQLAlchemy; 
    this has been `clarified <versioning_scheme>` in the documentation),
  * :ticket:`1130` modified calling signatures for most
    operations to consider all optional keyword parameters to
    be keyword-only arguments, to match what was always documented
    and generated by autogenerate. However, two of these
    changes were identified as possibly problematic without a
    more formal deprecation warning being emitted which were the
    ``table_name`` parameter to :meth:`.Operations.drop_index`,
    which was generated positionally by autogenerate prior to 
    version 0.6.3 released in 2014, and
    ``type_`` in :meth:`.Operations.drop_constraint` and
    :meth:`.BatchOperations.drop_constraint`, which was
    documented positionally in one example in the batch documentation.
  * Fixed typing use of :class:`~sqlalchemy.schema.Column` and
    other generic SQLAlchemy classes.
  * Restored the output type of :meth:`.Config.get_section` to
    include ``Dict[str, str]`` as a potential return type, which
    had been changed to immutable ``Mapping[str, str]``.
    When a section is returned and the default is not used,
    a mutable dictionary is returned.
  * Added placeholder classes for :class:`~.sqla.Computed` and
  * :class:`~.sqla.Identity` when older 1.x SQLAlchemy versions
    are in use, namely prior to SQLAlchemy 1.3.11 when the
    :class:`~.sqla.Computed` construct was introduced.
    Previously these were set to None, however this
    could cause issues with certain codepaths that were using
    ``isinstance()`` such as one within "batch mode".

buildservice-autocommit accepted request 1092850 from

Dirk Mueller (dirkmueller) 11 months ago (revision 145)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 11 months ago (revision 144)

- tag sle15 build for new python

buildservice-autocommit accepted request 1085181 from

Dirk Mueller (dirkmueller) 12 months ago (revision 143)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed 12 months ago (revision 142)

- update to 1.10.4:
  * Added support for autogenerate comparison of indexes on
    PostgreSQL which include SQL sort option, such as 
    ``ASC`` or ``NULLS FIRST``.
  * Fixed various typing issues observed with pyright, including
    issues involving the combination of :class:`.Function` and
    :meth:`.MigrationContext.begin_transaction`.
  * Fixed error raised by alembic when running autogenerate after
    removing a function based index.
  * Fixed regression where Alembic would not run with older
    SQLAlchemy 1.3 versions prior to 1.3.24 due to a 
    missing symbol. Workarounds have been applied for older
    1.3 versions.
  * Fixed issue regarding PostgreSQL :class:`.ExcludeConstraint`,
    where constraint elements which made use of :func:`.literal_column`
    could not be rendered for autogenerate. Additionally, using SQLAlchemy
    2.0.5 or greater, :func:`.text()` constructs are also supported within
    PostgreSQL :class:`.ExcludeConstraint` objects for autogenerate render.
  * Fixed issue in index detection where autogenerate change
    detection would consider indexes with the same columns but with
    different order as equal, while in general they are not equivalent
    in how a database will use them.
  * Recursive traversal of revision files in a particular
    revision directory is now supported, by indicating 
    ``recursive_version_locations = true`` in alembic.ini.
  * Fixed issue where indexes on SQLite which include SQL
    expressions would not compare correctly, generating false
    positives under autogenerate. These indexes are now skipped,
    generating a warning, in the same way that
    expression-based indexes on PostgreSQL are skipped and

buildservice-autocommit accepted request 1064239 from

Dirk Mueller (dirkmueller) about 1 year ago (revision 141)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed about 1 year ago (revision 140)

- update to 1.9.3:
  * Fixed issue where rendering of user-defined types
    that then went onto use the .with_variant() method would
    fail to render, if using SQLAlchemy 2.0's version of variants.

Displaying revisions 1 - 20 of 159

Places

Revisions of python-alembic

Places