9. Release Notes¶

9.1. MimerPy Version 1.1¶

MimerPy version 1.1 is the first public version.

Known problems:

DDL and DML statments can not be mixed in one transaction. DDL statements are always committed
DDL statements in a transaction can not be rolled back.
The methods setinputsizes() and setoutputsize() are not implemented for cursors.
Accessing values with the type builtin.uuid in Mimer SQL requires a MimerAPI of version 11.0.5B or later.
Accessing values with the type FLOAT(p) in Mimer SQL requires a MimerAPI of version 11.0.5B or later.
Accessing integer values larger than 2**63 with the type INTEGER(p) in Mimer SQL requires a MimerAPI of version 11.0.5B or later.
Using method callproc() to call a Stored Procedure is not yet supported.

MimerPy version 1.3.0 is a major release that uses ctypes and dynamic bindings to the Mimer SQL C API.

Major changes:

MimerPy is now implemented using ctypes to access the Mimer SQL C API. This removes the need for a C compiler on all platforms.
MimerPy now requires Python 3.6 or later.

MimerPy version 1.3.1 adds support for UUID and GIS datatypes in Mimer SQL and handles date, time, and timestamp correctly.

Major changes:

Support for the UUID datatype BUILTIN.UUID added.
Support for GIS datatypes added. This include BUILTIN.GIS_LOCATION, BUILTIN.GIS_LATITUDE, and BUILTIN.GIS_LONGITUDE. This requires Mimer SQL version 11.0.8E or later.
Date are mapped to Python date objects. Strings in the format ‘YYYY-MM-DD’ are also accepted when inserting DATE values.
Time are mapped to Python time objects. Strings in the format ‘HH:MM:SS[.ffffff]’ are also accepted when inserting TIME values.
Timestamp are mapped to Python datetime objects. Strings in the format ‘YYYY-MM-DD HH:MM:SS[.ffffff]’ are also accepted when inserting TIMESTAMP values.

MimerPy version 1.3.2 is a minor buggfix release that fix a problem with datetime in Python version 3.9 and older.

Minor changes:

MimerPy version 1.3.3 is a buggfix release that correct the behavior for fetchone()

Major changes:

fetchone() now returns None when no more rows are available, in accordance with the DB-API 2.0 specification.

MimerPy version 1.3.4 is a minor feature release that addes the optional cursor.lastrowid

Minoe changes:

cursor.lastrowid now return the auto generated primary key when doing and insert. The following conditions have to be met, otherwise None is returned:
- The primary key must have a default value with NEXT VALUE FOR <sequence>
- The primary key must be a single integer type column
- No value must be given for the primary key when inserting the row

MimerPy version 1.3.5 is a buggfix release that correct some data conversion issues

Major changes:

When setting parameters the following data conversion have been improved * It is possible to set all types that can be converted to a string on a string parameters * Integer, float, and double parameters now accepts string values representing a valid number. Integer also accept boolean

MimerPy version 1.3.6 is a feature release that add support for new datatypes and type helpers

Major changes:

MimerPy version 1.3.7 is a bugfix release that fixes a connection leak in the connection pool.

Bug fixes:

Fixed a leak where PooledConnection objects were not properly closed when the pool was discarding surplus connections. The __del__ method in MimerPool has been removed to avoid race conditions and to make connection lifecycle handling deterministic.

MimerPy version 1.3.8 drops support for Python 3.6 and fixes PEP 249 compatibility issues.

Major changes:

Minimum required Python version is now 3.7. Python 3.6 reached end-of-life in December 2021. Users still on Python 3.6 should pin mimerpy<1.3.
The python-dateutil dependency has been removed as it was only needed for Python 3.6 compatibility.

Bug fixes:

Connection.autocommit is now a read/write property as required by PEP 249. The old method-style conn.autocommit(True) is still supported for backward compatibility but is deprecated.
threadsafety is now an integer (1) as required by PEP 249, not a string.
Cursor.setinputsizes() now correctly accepts a sizes argument.
Cursor.setoutputsize() was incorrectly named setoutputsizes and did not accept the required size and optional column arguments. Both issues are now fixed.

MimerPy version 1.3.9 adds support for read-only connections and stored procedure calls.

Major changes:

Read-only connections are now supported via the readonly parameter to connect(). When readonly=True, all transactions are started with MIMER_TRANS_READONLY, which prevents any DDL or write DML operations on that connection. Combining readonly=True with autocommit=True raises a ProgrammingError.
Cursor.callproc() is now fully implemented. It supports stored procedures with IN, OUT, and INOUT parameters of any supported SQL type, as well as result-set procedures. OUT and INOUT parameter values are returned as a modified copy of the input sequence, as required by PEP 249.