Mimer SQL Data Provider
Corrected Problems
Mimer SQL Data Provider > Overview > Release Notes > Corrected Problems

Corrected problems in Mimer SQL Data Provider (11.0.4A):

  1. Fixed an issue in tracing where the trace system looked for a trace configuration file in the current working directory instead of the local application data folder if the local application data folder didn't exist.

Corrected problems in Mimer SQL Data Provider (11.0.3D):

  1. Fixed an IOException in tracing that was introduced in version 11.0.3A that occurred when the running Mimer.Data.Client application did not have write access to the roaming application data folder. Please note that in the new version tracing is configured from the local application data folder.
  2. Fixed connection inconsistencies that could occur when a MimerCommand.Cancel() request went wrong, which caused issues when trying to operate on the MimerConnection after the failed cancel request.

Corrected problems in Mimer SQL Data Provider (11.0.3C):

  1. Fixed a conversion issue between .NET double and single precision floats and Mimer SQL numeric floats introduced in version 11.0.3A.

Corrected problems in Mimer SQL Data Provider (11.0.3B):

  1. Fixed a build issue that was introduced in the NuGet package in 11.0.3A that caused issues with negative signs in conversions between strings and numeric data types.
  2. Fixed an issue where a FLOAT column from a Mimer SQL 10.1 server could not be fetched into a decimal with GetDecimal.

Corrected problems in Mimer SQL Data Provider (11.0.3A):

  1. If an SQL compilation returns a large number of select items, and information about these do not fit in the current network package, the client will now automatically retry the compilation with a network package that is sufficiently large. Previously error code -19053, "Output descriptor overflow" was returned.
  2. All shared libraries in the distribution are now properly signed with a digital signature.
  3. When logging into the database server using Integrated Security it was previously only possible to use the same name in Mimer SQL as the operating system user. It is recommended that you always specify User Id in the connection string, regardless if using Integrated Security or not.
  4. Assemblies for .NET Core and .NET 5 are now correctly signed with a private key. Public key token has value 36741a5a4e9064f1 as for other Mimer SQL Data Provider assemblies.
  5. DataSourceInformation attribute GroupByBehavior that is returned by MimerConnection.GetSchema has been corrected to GroupByBehavior.MustContainAll to reflect the SQL dialect used by Mimer SQL.
  6. If the same named parameter is used in more than one of the statements in a multi-SQL statement, it is now correctly interpreted as one single parameter and only has to be defined once. It is also no longer allowed to have several parameters with the same name.
  7. Fixed a number of issues where the last decimal places were incorrect when converting between different floating point data types in the .NET Core 3.1 and .NET 5 providers.
  8. The installation once again installs the Mimer SQL ADO.NET Provider documentation in the Visual Studio Help viewer. The same help viewer is used for Visual Studio 2017, 2019, and 2022 so the documentation is either present in all or none of them.
  9. Fixed an issue on Windows (all .NET versions) and Linux (.NET 5 and later), when using a culture that uses another negative sign than U+002D HYPHEN-MINUS (e.g. U+2212 MINUS SIGN used by the sv-SE culture) where retrieving error messages for negative server error codes failed. This remains an issue on Linux for .NET Core 3.1, see Known Problems.

Corrected problems in Mimer SQL Data Provider (11.0.1B):

  1. The Mimer SQL Monitor is now placed in the correct directory to be able to find the provider DLLs.
  2. The nuget packages are now signed properly.
  3. Distributed transaction handling can now properly handle parallel connections toward a single database server. Previously error code that the transaction id, XID, could not be found was returned.

Corrected problems in Mimer SQL Data Provider (11.0.1A):

  1. When reading large results set from server in an auto-committed transaction each set of rows (eg. 10-200 rows) was executed in its own transaction. I.e. it would be possible to see changes from later transactions in the subsequence sets read from the server. Now a query is executed in one auto-committed transaction.

Corrected problems in Mimer SQL Data Provider (10.1.2A):

  1. When converting from an invalid floating point value, i.e. NAN (Not A Number), the error handling now gives ArgumentOutOfRange exception.
  2. All assemblies are now signed with both SHA1 and SHA2 digital signatures.

Corrected problems in Mimer SQL Data Provider and (10.1.1A):

  1. Handshake communication is now synchronized internally during MimerConnection.Open.
  2. Error handling during handshake processing is updated so that error codes are preserved properly.

Corrected problems in Mimer SQL Data Provider and (10.1.0C):

  1. Comments are now supported in the DbProviderSection of machine.config.

Corrected problems in Mimer SQL Data Provider and (10.1.0B):

  1. The MimerConnectionStringBuilder.Remove method did not correctly remove the requested item. This had strange effects on the connection dialog used by the Visual Studio server explorer. This is now corrected along with proper return code for the operation.
  2. No registry entries are now stored under compact framework registry keys.
  3. Uninstallation of the Mimer SQL Data Provider now leaves the registry in a consistent state.
  4. It is now possible to first install Mimer SQL Data Provider, then Visual Studio, followed by a repair of Mimer SQL Data Provider. The repair will correctly register the data provider with Visual Studio 2010.

Corrected problems in Mimer SQL Data Provider and (10.1.0A):

  1. An internal lock is now taken by the MimerConnection class when releasing statement handles in the server. This secures the case where a parallel dispose is made by the garbage collector. This could cause the same statement to be incorrectly freed twice.
  2. When auto-commit is used with read cursor the transaction was not always terminated properly when MimerDataReader.Close was called. This occurred in cases where the last call to the server did not return zero rows or when there were large objects present in the result set.
  3. When connecting to an old Mimer SQL server (i.e. 9.2) the handshake processing did not handle the connection properly resulting in a "server is closed" error message. This has now been corrected.
  4. When installing on a machine without Visual Studio accessing the documentation previously caused a repair of the installation. This will no longer occur.