Posted by Gerhard Stephan on 13th July 2008
This release covers a lot of smaller and bigger bug fixes for the Microsoft SQL Server 2000 and 2005.
Some Statements could not be executed for the Microsoft SQL Server 2000 by the SqlFile class, because the SQLs that have been executed all ends with a semicolon. Microsoft SQL Server 2005 doesn’t care about, but Microsoft SQL Server 2000 ends up with a failure. This bug has been fixed by removing the semicolon at the end for all databases but Oracle.
The integration check for Microsoft Access failed when a field had a property length greater than 255. Thus forces the Microsoft Access Persister to use a MEMO field, but the integration check did not care about that and throwed a failure, because the max size of a memo field differed to the max size of an integer value. This bug has been fixed by updating the integration check which now takes care to that issue.
Another bug was that the SqlTracer did not take care of the formatting of SQL Statements for the Microsoft Sql Server. It was not everytime possible to use the trace output as a direct input for SQL queries used by the Microsoft SQL Server. This problem has been fixed by changing the parameter formatting for the Microsoft SQL Server.
Furthermore there had been a failure, if the SQL Tracer outputs SQL Statements which uses a parameter more than one time. As a result the second parameter use haven’t been replaced with the concret value by the SQL Tracer. This bug has also been fixed now.
The fith bug has been fixed for the Microsoft SQL Server 2000. The Microsoft SQL Server 2000 has problems to parse a select statement like SELECT TOP(x). The select statement has been changed so that it fits the needs for the Microsoft SQL Server 2000.
If you find some more bugs, please don’t hesitate to report them into the forum of the ObjectMapper .NET.