Sqlalchemy-hana

Latest version: v3.0.0

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

1.2.0

-----

Features
~~~~~~~~
- Support CREATE and DROP of views
- Add limited UPSERT support
- Add support for exception wrapping by replacing hdbcli errors with more detailed ones if possible

1.1.1

-----

Bugfixes
~~~~~~~~
- Fixed an issue causing the alembic dialect to render a ``RENAME`` table statement wrongly

1.1.0

-----

Features
~~~~~~~~
- The statement caching capabilities of SQLAlchemy are now supported
- Calculated/Computed columns are now officially supported
- The following SAP HANA types are now supported: ``SECONDDATE``, ``LONGDATE`` and ``ALPHANUM``
- The module ``sqlalchemy_hana.types`` defines now all SAP HANA native types
- All *camelcase* types of SQLAlchemy are now supported. If SAP HANA does not support it, a
similar type is used automatically
- sqlalchemy-hana will now expose the version information of the connected SAP HANA instance,
filling the dialect field ``server_version_info``

Bugfixes
~~~~~~~~
- During column reflection all types will expose their respective length, scale and precision

1.0.1

-----

Bugfixes
~~~~~~~~
- Version 1.0.0 states that ``is_distinct_from`` is supported, but the dialect specified
``supports_is_distinct_from=False``. The value was changed to ``True``
- Fixed an issue causing ``is_not_distinct_from`` to fail with an SQL syntax error
- Make sure that ``Text`` types are really rendered as ``UnicodeText``
- Removed misleading ``get_dbapi_type`` from ``Boolean``

1.0.0

-----

Breaking Changes
~~~~~~~~~~~~~~~~
- By default native booleans are used. If integer based columns should be used, specify
``use_native_boolean=False`` in ``create_engine``
- Columns of SQLAlchemy type String are now created with the SAP HANA SQL type NVARCHAR.
The previously used SAP HANA SQL type VARCHAR has been only designed for 7-bit ASCII character data.
Storing other non-ASCII characters in a different encoding like UTF-8 was sometimes possible but
never intended or recommended
It may cause unexpected behavior for certain database-side operations like sorting or failures
with string functions
With the introduction of SAP HANA Cloud, the SQL type VARCHAR is also only an alias for NVARCHAR.
- Columns of SQLAlchemy type Text are now created with the SAP HANA SQL type NCLOB instead of CLOB.
Like the SAP HANA SQL type VARCHAR, CLOB was designed for 7-bit ASCII character data.
This change also ensures consistency and compatibility with SAP HANA Cloud, where CLOB is just an
alias for NCLOB
- Removed ``pyhdb`` support because ``pyhdb`` is out of maintenance and the GitHub repository was
archived.
Please migrate to ``hdbcli`` as it also supports connections towards SAP HANA Cloud databases.
- Removed support for Python versions below version 3.8
- Removed support for SQLAlchemy below version 1.4
- Removed support for hdbcli below version 2.10
- Removed the hidden and outdated feature ``auto_convert_lobs``

Features
~~~~~~~~
- Official support for SQLAlchemy 1.4 and 2.0
- Official support for Python 3.11 and 3.12
- Support the SAP HANA datatype ``SMALLDECIMAL``
- Support native booleans (this is the new default)
- The ``sqlalchemy_hana`` package is fully typed and exports its types
- The Alembic dialect left the preview stage and is now included by default.
Please install sqlalchemy-hana with the alembic requirement like ``pip install sqlchemy-hana[alembic]``.
Supported is Alembic 1.12 onwards.
- Specified the SQLAlchemy statement caching support explicitly to false.
Support might be added later (see 126)
- Support `regexp_match <https://docs.sqlalchemy.org/en/20/core/operators.html#string-matching>`_
and `regexp_replace <https://docs.sqlalchemy.org/en/20/core/operators.html#string-alteration>`_
- Allow usage of ``is_distinct_from`` operator through a SAP HANA compatible expression
- Prefer dialect types in ``get_columns``
- Allow usage of additional options (e.g. ``nowait``) in ``with_for_update`` when using
``read=True``
- Added CI with linters and testing utilizing the SQLAlchemy and Alembic test suite

Bugfixes
~~~~~~~~
- Fixed a bug with SQLAlchemy's custom AUTOCOMIT isolation level. If the user changed the isolation
level from AUTOCOMMIT to something else, the dialect didn't notified the underlying database
connection and it stayed in autocommit mode while the user expected the typical transaction
behavior and the defined isolation level.

0.5.0

-----
- Improved support for ''SELECT FOR UPDATE'' statements.

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.