mxODBC Connect Change Log

The change log includes a detailed description of all changes to this package in the recent releases.

Version: 2.0.0

Changes from 1.0.2 to 2.0.0:

mxODBC Connect Server is now also available as native 64-bit build for Windows 2008R2, Vista and 7 x64.
All mxODBC Connect Server executables are now signed on Windows to reduce the number of UAC dialogs during installation and use.
The mxODBC Connect tray app was rewritten in C to reduce the memory footprint.
The mxODBC Connect Server tray application was updated to work on Windows 7 as well.
mxODBC Connect now supports Python 2.7 both on the client and server side.
mxODBC Connect Server now supports unixODBC 2.3 or later on Unix platforms. unixODBC 2.2 is no longer supported on 64-bit systems.

mxODBC Connect Server now uses mxODBC 3.2 internally and makes its API available in the mxODBC Connect Client. This is a major step forward from the mxODBC 3.0 version used in mxODBC Connect Server 1.0.
mxODBC Connect Server now features all the ODBC driver compatibility enhancements provided by mxODBC 3.2, including better support for MS SQL Server Native Client, Oracle Instant Client, Sybase ASE, IBM DB2, Teradata and Netezza.
mxODBC Connect Client comes with all mxODBC 3.2 enhancements, including:

connection and cursor objects can be used as context managers
adjustable parameter styles (qmark or named)
connection .autocommit attribute to easily switch on autocommit
adjustable timestamp resolution
new possibilities to set connection and cursor options to adjust the ODBC objects to your application needs, e.g. set a connection read-only or set a query timeout
adjustable decimal, datetime and string formats
adjustable warning format to be able to handle server warnings without client interaction
greatly improved result set scrolling support
Unicode support for all catalog methods
Access to additional result set meta data via cursor.getcolattribute()

mxODBC Connect Client now integrates directly with gevent, allowing client applications to run asynchronous tasks while performing remote database queries.
mxODBC Connect Client also works with a monkey-patched gevent environment.

mxODBC Connect now uses the official IANA registered port 6632 (mxodbc-connect) for both plain text and SSL-encrypted communication.
Added STARTTLS support to be able to use a single port for both unencrypted and SSL-encrypted communication.
mxODBC Connect Client no longer requires a client certificate and key for SSL connections.
mxODBC Connect Client now allows selecting the used SSL module from two available options: Python standard lib ssl module and pyOpenSSL.
Upgraded to pyOpenSSL 0.13.0-1.0.0j on the server side.
mxODBC Connect Server will now use SHA1 digests for client certificate checks instead of MD5 to improve security.
mxODBC Connect Client can now additionally read client certificate and private key from the config_data dictionary instead of from files only - provided that pyOpenSSL is used (Python's ssl module doesn't support this).
Client certificate checks are now also supported when using the standard Python ssl module on the client side.

mxODBC Connect Server will now return ProtocolErrors to the client side and close the connection in case it finds that it cannot decode the client side pickle.
Fixed a problem with database connections being kept alive in sessions that were not explicitly closed by the client application.
mxODBC Connect pure Python prebuilt archives did not always install on non-Linux platforms.
ServerSession.close() will no longer cause error messages at Python exit time, if the close action cannot be communicated to the server.
mxODBC Connect Client will now raise a mx.ODBCConnect.Error.ConnectionFailureError in case of server connection failures due to timeouts.
Fixed a bug in session.open() which caused the module_name parameter not to get used.

Python 2.3 and 2.4 support was removed from mxODBC Connect Client.
The start menu entry on Windows now includes a link to the correct ODBC manager to be used with mxODBC Connect Server. This helps finding the right one on Windows x64 platforms which provide two versions.
mxODBC Connect Client will now directly install into the correct directories on Linux distributions that use different directories for platform dependent and non-dependent directories (e.g. 64-bit RedHat and 64-bit OpenSUSE), without needing additional options on the install command.
Added backwards compatibility support for the old-style using_ssl way of configuring server connections.

Upgraded the eGenix pyOpenSSL version included in mxODBC Connect Server to 0.9.0-0.9.8k
Fixed a problem with connections sometimes timing out after 10 seconds of inactivity.
Connection errors now cause an implicit immediate close of the connection (without having to wait for a timeout). This allows the client to shutdown much faster when exiting the Python client application in the situation of a broken server connection.
Clarified the INI file format used by mxODBC Connect Server and Client and added an extra section for this to the documentation.

Added cursor iterator support to mxODBC Connect Client.
Upgraded mxODBC version included in mxODBC Connect Server to 3.0.3
Fixed a problem with database connections being kept alive in sessions that were not explicitly closed by the client application.
Fixed a bug in print_resultset() due to a missing import in one of the modules.
mxODBC Connect Client prebuilt archives failed to install on non-Linux platforms.
mxODBC Connect Client's ServerSession.close() will no longer cause error messages at Python exit time, if the close event cannot be communicated to the server.

Further improved the mxODBC Connect network layer, resulting in much better fetch and round-trip performance, esp. for SSL connections
Improved the documentation, added screenshots and more configuration notes as well as tips on how to tune the network performance
Fixed a problem with a full Windows event log causing the mxODBC Connect Server not to start
The main_timeout configuration setting in both client and server configurations was split into send_timeout and receive_timeout for better customization on asymmetric network setups
The default for the client's server_connections configuration option now is the sorted list of connection section names

Contact : Impressum : Terms & Conditions : Privacy Policy : Trademarks 2024-10-09