| Change type |
Package |
Component |
For build |
Logged on |
Change text |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
02012013 |
01-Feb-2013 |
Linq, Oracle DQEs: The DateTime.Date property function mapping lacked a TRUNC() wrapping, so the time portion of a value was not cropped, leading to invalid results or wrong queries. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
12042012 |
04-Dec-2012 |
Fixed quote issue in DB2 schema names. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
11202012 |
20-Nov-2012 |
Inheritance: in an edge-case it could be inheritance relationships weren't added for a TPE subtype if the projection contained fields from the root type and a where clause contained fields from a subtype and the query was in a derived table. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
10152012 |
15-Oct-2012 |
When the PK field of entity E had a typeconverter defined, fetching excluded fields into instances of E could fail. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
08062012 |
06-Aug-2012 |
DB2, Linq: Some function mappings containing CASE expressions were sometimes using the DB2 CASE statement syntax which could cause a query to fail. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
07182012 |
18-Jul-2012 |
Linq, MS Access, MySQL: Using the .Trim() method on a string typed field/variable, could cause a problem in the resulting query due to a typo in the function mapping. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
07162012 |
16-Jul-2012 |
Oracle DQE: in some situations it could be that the DQE introduced too many quotes around the schema names which was introduced after a bugfix on March 12th. V3.5 doesn't have this problem. |
| Fix |
Documentation 3.1 |
Documentation 3.1 |
05142012 |
14-May-2012 |
Typo fix in selfservicing example in docs. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
05072012 |
07-May-2012 |
Linq: A predicate specification of the form: 'value > field' would result in a predicate of the form: 'field <= value'. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
04162012 |
16-Apr-2012 |
Decimal/Single/Double scale correction on a negative value could lead an incorrect ArgumentOutOfRangeException. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
03152012 |
15-Mar-2012 |
Stored procedure calls: when a nullable enum typed parameter was used as an output parameter, it could be the fetch caused an invalid cast exception because Nullable has insufficient implicit conversion operators. We added workaround code to cover this scenario. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
03122012 |
12-Mar-2012 |
When a space was present in the catalog or schema name the catalog/schema name overwrites should be using and a stored procedure was called and the name was supplied through the hashtable meant for this purpose, the catalog and/or schema name wasn't properly wrapped in alias brackets/quotes causing a problem when executing the stored procedure. |
| Fix |
Designer 3.1 |
Designer Core 3.1 |
March 12rh, 2012 |
12-Mar-2012 |
When an FK constraint had at least one FK field pointing to itself, but also at least one FK field not pointing to itself, it was still considered an illegal relationship, although it is usable in practice. |
| Fix |
Designer 3.1 |
Designer Core 3.1 |
March 12th, 2012 |
12-Mar-2012 |
When a relationship had at least one field pointing to itself (which is wrong in theory, but in practice most DB's support it), no FK constraint was created from it. |
| Change |
Designer 3.1 |
Designer GUI 3.1 |
February 24th, 2012 |
24-Feb-2012 |
VB.NET language no longer auto-corrects casing in the text editor. |
| Fix |
Designer 3.1 |
Designer Core 3.1 |
February 22nd, 2012 |
22-Feb-2012 |
When a parameter was removed on a stored procedure in the RDBMS and a refresh was performed and the preference/project setting 'RemoveUnmappedElementsAfterRefresh' was set to false, the mapped call would end up with an unmapped parameter which wasn't removable. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
02222012 |
22-Feb-2012 |
Oracle DQEs: Marking an output parameter on a stored procedure call as 'Optional' could cause a cast exception when the procedure was called at runtime |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
02162012 |
16-Feb-2012 |
Linq, Oracle: using metaData.Entity.Any(), a boolean should be returned however the provider could crash if the returned value from the EXISTS query is not an int32. In case of Oracle this could be a decimal, which caused the projection engine to throw an invalidcastexception |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
02162012 |
16-Feb-2012 |
In an edge case where in a prefetch path 2 nodes were fetched which are related over an m:n relationship and where both nodes are of a type which are siblings of each other in an inheritance hierarchy and a filter was added for the node, the query could fail due to the re-use of an alias in the subquery instead of issuing a new alias. |
| Fix |
Templates 3.1 |
Templates 3.1 |
02062012 |
06-Feb-2012 |
LLBLGen Pro Runtime framework: In the edge case when the catalog name contained a '\' character, the C# generated code could become uncompilable. |
| Fix |
Drivers 3.1 |
Drivers 3.1 |
02062012 |
06-Feb-2012 |
MS Access driver: the driver required the username to be filled in before the Test Connection button was enabled, while the user name isn't always required. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
01192012 |
19-Jan-2012 |
SQL Server specific: when using catalog name or schema name overwriting and stored procedures, the new stored procedure name could contain catalog and/or schema names which weren't wrapped in [], which could cause problems when the new schema / catalog name contains spaces or other non-alphanumeric characters. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
01102012 |
11-Jan-2012 |
Linq: the preprocessor is now more robust as it can handle in-memory candidates better. |
| Fix |
Runtime Libraries 3.1 |
Runtime Libraries 3.1 |
01102012 |
10-Jan-2012 |
Linq: when a method was used to build a lambda predicate and the lambda predicate was passed to an aggregate function the preprocessor failed. |
| Fix |
Templates 3.1 |
Templates 3.1 |
01042012 |
04-Jan-2012 |
Linq to Sql: When a navigator on the fk side of a relationship was hidden, code generated might not compile properly. |