---
- branch: MAIN
  date: Tue Jan 15 11:51:27 UTC 2019
  files:
  - new: '1.48'
    old: '1.47'
    path: pkgsrc/databases/py-sqlalchemy/Makefile
    pathrev: pkgsrc/databases/py-sqlalchemy/Makefile@1.48
    type: modified
  - new: '1.43'
    old: '1.42'
    path: pkgsrc/databases/py-sqlalchemy/distinfo
    pathrev: pkgsrc/databases/py-sqlalchemy/distinfo@1.43
    type: modified
  id: 20190115T115127Z.d2001410c2fa71f7b30f9a354c27e01a88fe5cfb
  log: "py-sqlalchemy: updated to 1.2.16\n\n1.2.16:\nengine\n\n[engine] [bug] Fixed
    a regression introduced in version 1.2 where a refactor of the SQLAlchemyError
    base exception class introduced an inappropriate coercion of a plain string message
    into Unicode under python 2k, which is not handled by the Python interpreter for
    characters outside of the platform窶å\x86± encoding (typically ascii). The SQLAlchemyError
    class now passes a bytestring through under Py2K for __str__() as is the behavior
    of exception objects in general under Py2K, does a safe coercion to unicode utf-8
    with backslash fallback for __unicode__(). For Py3K the message is typically unicode
    already, but if not is again safe-coerced with utf-8 with backslash fallback for
    the __str__() method.\n\nsql\n\n[sql] [bug] [mysql] [oracle] Fixed issue where
    the DDL emitted for DropTableComment, which will be used by an upcoming version
    of Alembic, was incorrect for the MySQL and Oracle databases.\n\npostgresql\n\n[postgresql]
    [bug] Fixed issue where a postgresql.ENUM or a custom domain present in a remote
    schema would not be recognized within column reflection if the name of the enum/domain
    or the name of the schema required quoting. A new parsing scheme now fully parses
    out quoted or non-quoted tokens including support for SQL-escaped quotes.\n\n[postgresql]
    [bug] Fixed issue where multiple postgresql.ENUM objects referred to by the same
    MetaData object would fail to be created if multiple objects had the same name
    under different schema names. The internal memoization the PostgreSQL dialect
    uses to track if it has created a particular postgresql.ENUM in the database during
    a DDL creation sequence now takes schema name into account.\n\nsqlite\n\n[sqlite]
    [bug] Reflection of an index based on SQL expressions are now skipped with a warning,
    in the same way as that of the Postgresql dialect, where we currently do not support
    reflecting indexes that have SQL expressions within them. Previously, an index
    with columns of None were produced which would break tools like Alembic.\n\nmisc\n\nFixed
    issue in 窶彳xpanding IN窶� feature where using the same bound parameter
    name more than once in a query would lead to a KeyError within the process of
    rewriting the parameters in the query\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/databases/py-sqlalchemy'
  unixtime: '1547553087'
  user: adam