openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of python-alembic

Dirk Mueller (dirkmueller) committed over 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.

buildservice-autocommit accepted request 1061744 from

Dirk Mueller (dirkmueller) over 1 year ago (revision 139)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed over 1 year ago (revision 138)

- update to 1.9.2:
  * Fixed typing definitions for :meth:`.EnvironmentContext.get_x_argument`.
    Typing stubs are now generated for overloaded proxied methods such as
  * Fixed regression caused by :ticket:`1145` where the string transformations
    applied to server defaults caused expressions such as ``(getdate())`` to no
    longer compare as equivalent on SQL Server, others.

buildservice-autocommit accepted request 1058079 from

Factory Maintainer (factory-maintainer) over 1 year ago (revision 137)

baserev update by copy to link target

buildservice-autocommit accepted request 1056257 from

Markéta Machová (mcalabkova) over 1 year ago (revision 136)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed over 1 year ago (revision 135)

- update to 1.9.1:
    .. change::
        :tickets: 1145
        Fixed issue where server default compare would not work for string defaults
        that contained backslashes, due to mis-rendering of these values when
        comparing their contents.
    .. change::
        :tags: bug, oracle
        Implemented basic server default comparison for the Oracle backend;
        previously, Oracle's formatting of reflected defaults prevented any
        matches from occurring.
    .. change::
        :tags: bug, sqlite
        Adjusted SQLite's compare server default implementation to better handle
        defaults with or without parens around them, from both the reflected and
        the local metadata side.
    .. change::
        :tags: bug, mssql
        Adjusted SQL Server's compare server default implementation to better
        handle defaults with or without parens around them, from both the reflected
        and the local metadata side.

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

Yogalakshmi Arunachalam (yarunachalam) over 1 year ago (revision 134)

- Update to 1.9.0: 
  feature
  * Added new Alembic command alembic check. This performs the widely requested feature of running an “autogenerate” comparison
    between the current database and the MetaData that’s currently set up for autogenerate, returning an error code if the two do not match,
    based on current autogenerate settings. Pull request courtesy Nathan Louie.
    See also Running Alembic Check to test for new upgrade operations
    References: #724
    bug
  * Fixed issue in tox.ini file where changes in the tox 4.0 series to the format of “passenv” caused tox to not function correctly,
    in particular raising an error as of tox 4.0.6.
  * Fixed typing issue where revision.process_revision_directives was not fully typed; additionally ensured all Callable and Dict arguments
    to EnvironmentContext.configure() include parameters in the typing declaration.
    Additionally updated the codebase for Mypy 0.990 compliance.
    References: #1110

buildservice-autocommit accepted request 992110 from

Dirk Mueller (dirkmueller) almost 2 years ago (revision 133)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed almost 2 years ago (revision 132)

- update to 1.8.1:
  * Fixed bug where the SQLite implementation of
    :meth:`.Operations.rename_table` would render an explicit schema name for
    both the old and new table name, which while is the standard ALTER syntax,
     is not accepted by SQLite's syntax which doesn't support a rename across
    schemas. In particular, the syntax issue would prevent batch mode from
    working for SQLite databases that made use of attached databases (which are
    treated as "schemas" in SQLAlchemy).
  * Added an error raise for the condition where
    :meth:`.Operations.batch_alter_table` is used in ``--sql`` mode, where the
    operation requires table reflection, as is the case when running against
    SQLite without giving it a fixed ``Table`` object. Previously the operation
    would fail with an internal error.   To get a "move and copy" batch
    operation as a SQL script without connecting to a database,
    a ``Table`` object should be passed to the
    :paramref:`.Operations.batch_alter_table.copy_from` parameter so that
    reflection may be skipped.

buildservice-autocommit accepted request 980910 from

Matej Cepl (mcepl) almost 2 years ago (revision 131)

baserev update by copy to link target

Matej Cepl (mcepl) accepted request 980809 from

Arun Persaud (apersaud) almost 2 years ago (revision 130)

update to latest version

buildservice-autocommit accepted request 965089 from

Dirk Mueller (dirkmueller) about 2 years ago (revision 129)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed about 2 years ago (revision 128)

- update to 1.7.7:
  * Fixed issue where using :meth:`.Operations.create_table` in conjunction
    with a :class:`.CheckConstraint` that referred to table-bound
    :class:`.Column` objects rather than string expressions would be added to
    the parent table potentially multiple times, resulting in an incorrect DDL
    sequence. Pull request courtesy Nicolas CANIART.
  * The ``logging.fileConfig()`` line in ``env.py`` templates, which is used
    to setup Python logging for the migration run, is now conditional on
    :attr:`.Config.config_file_name` not being ``None``.  Otherwise, the line
    is skipped as there is no default logging configuration present.
  * Fixed bug where an :meth:`.Operations.alter_column` operation would change
    a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that
    did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was
    implicitly assuming "NULL"). An :meth:`.Operations.alter_column` operation
    that specifies :paramref:`.Operations.alter_column.type` should also
    specify include either :paramref:`.Operations.alter_column.nullable` or
    :paramref:`.Operations.alter_column.existing_nullable` to inform Alembic as
    to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning
    is now emitted if this is missing under this scenario.

Dirk Mueller (dirkmueller) committed over 2 years ago (revision 127)

- update to 1.7.6:
  * Add a new command alembic ensure_version, which will ensure that the Alembic
    version table is present in the target database, but does not alter its
    contents.
  * Fixed regression where usage of a with_variant() datatype in conjunction with
    the existing_type option of op.alter_column() under batch mode would lead to an
    internal exception.
  * Implemented support for recognizing and rendering SQLAlchemy “variant” types
    going forward into SQLAlchemy 2.0, where the architecture of “variant”
    datatypes will be changing.
  * Added a rule to the MySQL impl so that the translation between JSON / LONGTEXT
    is accommodated by autogenerate, treating LONGTEXT from the server as
    equivalent to an existing JSON in the model.
  * Removed a warning raised by SQLAlchemy when dropping constraints on MSSQL
    regarding statement caching.

Dirk Mueller (dirkmueller) committed over 2 years ago (revision 126)

- update to 1.7.5:
  * Adjustments to the test suite to accommodate for error message change 
    in newer SQLAlchemy

Dirk Mueller (dirkmueller) accepted request 929862 from

Benjamin Greiner (bnavigator) over 2 years ago (revision 125)

- Update requirements
- Remove unused python-alembic-rpmlintrc

Dirk Mueller (dirkmueller) committed over 2 years ago (revision 124)

- update to 1.7.4:
  * Fixed a regression that prevented the use of post write hooks on python
    version lower than 3.9 
  * Added missing attributes from context stubs.
  * Fixed issue where registration of custom ops was prone to failure due to
    the registration process running exec() on generated code that as of the
    1.7 series includes pep-484 annotations, which in the case of end user code
    would result in name resolution errors when the exec occurs

Dirk Mueller (dirkmueller) accepted request 916927 from

Arun Persaud (apersaud) over 2 years ago (revision 123)

update to latest version

buildservice-autocommit accepted request 897867 from

Dirk Mueller (dirkmueller) almost 3 years ago (revision 122)

baserev update by copy to link target

Dirk Mueller (dirkmueller) committed almost 3 years ago (revision 121)

- update to 1.6.5:
  * feature
    + [feature] [autogenerate] Fix the documentation regarding the
      default command-line argument position of the revision script
      filename within the post-write hook arguments. Implement a
      REVISION_SCRIPT_FILENAME token, enabling the position to be
      changed. Switch from str.split() to shlex.split() for more
      robust command-line argument parsing.
    + [feature] Implement a .cwd (current working directory) suboption
      for post-write hooks (of type console_scripts). This is useful
      for tools like pre-commit, which rely on the working directory
      to locate the necessary config files. Add pre-commit as an
      example to the documentation. Minor change: rename some
      variables from ticket #819 to improve readability.
  * bug
    + [bug] [autogenerate] Refactored the implementation of
      MigrateOperation constructs such as CreateIndexOp,
      CreateTableOp, etc. so that they no longer rely upon maintaining
      a persistent version of each schema object internally; instead,
      the state variables of each operation object will be used to
      produce the corresponding construct when the operation is
      invoked. The rationale is so that environments which m

Displaying revisions 21 - 40 of 160

Places

Revisions of python-alembic

Places