Fix |
Templates 4.2 |
Templates 4.2 |
10232014 |
23-Oct-2014 |
LLBLGen Pro Runtime Framework, PostgreSql: output parameters in stored procedures were generated as elements of the signature of the proc due to requirements of old npgsql versions however this creates problems on newer versions. This fix makes the procs work on v2.x npgsql. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10232014 |
23-Oct-2014 |
Linq: in an edge case it could be a join was appended to a derived table join which would go wrong in an inheritance scenario if the join was embedded in a derived table in a specific situation. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10232014 |
23-Oct-2014 |
DB2: excluded fields would result in NULL AS <name> but DB2 requires a type cast around the NULL value. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10222014 |
22-Oct-2014 |
Linq: in an edge case it could be a nested projection didn't use the proper alias. This occurred in situations where a join was followed by a where / order by method which full query was then followed by an aggregate method or e.g. an Any() call. |
Fix |
Templates 4.2 |
Templates 4.2 |
10202014 |
20-Oct-2014 |
NHibernate, SQL Server: db fields of type 'datetime2' now get a specific type specification in hbm and fluent mappings. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10172014 |
17-Oct-2014 |
QuerySpec: specifying qf.EntityName.Select(Functions.CountRow()) where EntityName was a name of an entity in an inheritancy hierarchy of TPEH type, didn't append the proper type filter. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10172014 |
17-Oct-2014 |
Linq: appending Count to a custom projection into an entity type which was in a TPEH hierarchy could lead to duplicate or wrong type filters being applied.
|
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
10172014 |
17-Oct-2014 |
Fixed issue where a TPEH projection in a derived table would not have typefilters present, causing appended aggregate functions and / or projections to return the wrong results. |
Change |
Designer 4.2 |
Designer GUI 4.2 |
October 3rd, 2014 |
06-Oct-2014 |
VS.NET Integration: When a tab is added/removed/activated in the designer tab well, the vs.net tab for the designer is activated, to make it unhidden if another tab was in front of it in vs.net. |
Fix |
Templates 4.2 |
Templates 4.2 |
09242014 |
24-Sep-2014 |
LLBLGen Pro Runtime Framework settings: The Output Type for a Typed List wasn't selectable from a drop down list in the Code Generation Info tab. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
09192014 |
19-Sep-2014 |
Linq: When a nested query in the projection used a multi-predicate filter with an OR, additionally to the correlation predicate, the OR operand could be ignored for the nested query, causing the wrong where clause to be generated. |
Fix |
Designer 4.2 |
Designer GUI 4.2 |
September 15th, 2014 |
15-Sep-2014 |
When 'Expand group nodes on project load' was unchecked, the groups should have been collapsed after load of a project, but instead they were fully expanded, due to a bug in the caching mechanism for expanded nodes. |
Fix |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
09032014 |
03-Sep-2014 |
OracleDQE / Linq: the function mapping for the DateTime.Add* functions used INTERVAL which didn't work for parameterized queries. |
Fix |
Designer 4.2 |
Designer Core 4.2 |
September 3rd, 2014 |
03-Sep-2014 |
The fix from August 6 had a side effect that in some cases newly retrieved metadata would mark PK constraint names as 'changed', which would lead to the relational model data being marked as 'changed' so it required an UPDATE DDL SQL script export. |
Addition |
Documentation 4.2 |
Documentation 4.2 |
08292014 |
29-Aug-2014 |
LLBLGen Pro Runtime Framework: added Note to make sure it's clear '!/Not' alter the predicate they're used with, and don't create a copy of the predicate they're used with. |
Fix |
Designer 4.2 |
Designer GUI 4.2 |
August 27th, 2014 |
27-Aug-2014 |
The element retrieval editor for reverse engineering elements wasn't centered to its parent in some cases. |
Change |
Designer 4.2 |
Designer Core 4.2 |
August 26th, 2014 |
26-Aug-2014 |
The designer saved the project unattended when integrated inside VSNET which would then popup a dialog that the file was changed. This has been changed: the designer now doesn't auto-save the project after code generation when integrated in vs.net, and before refreshing the catalog it will only save the project to the backup file, not to the real file. |
Fix |
Designer 4.2 |
Designer GUI 4.2 |
August 25th, 2014 |
25-Aug-2014 |
In some cases setting the preferred project path in the preferences was not working. |
Addition |
Runtime Libraries 4.2 |
Runtime Libraries 4.2 |
08112014 |
11-Aug-2014 |
Linq: Added check for factory retrieval fail to make error detection easier with linq queries based on interfaces. |
Fix |
Task Performers 4.2 |
Code generator 4.2 |
08082014 |
08-Aug-2014 |
.lpt templates which are marked as 'includeOnly' and which can't stand on their own as a separate class could lead to a crash during code generation because the templates were still converted as separate classes for include into TDL templates. |
Fix |
Designer 4.2 |
Designer Core 4.2 |
August 8th, 2014 |
08-Aug-2014 |
Catalog refresher, Sequence pattern: When a sequence was assigned manually to a field mapping and the sequence pattern defined in the project settings would lead to no matching sequence in the meta-data for the particular field mapping, the manually assigned sequence was removed from the field mapping. This has now been corrected: manually assigned sequences are no longer reset if the sequence pattern doesn't match any sequence in the metadata. |
Fix |
Designer 4.2 |
Designer Core 4.2 |
August 6th, 2014 |
06-Aug-2014 |
In some edge cases it could be a pk constraint was found as changed (due to multiple pk constraint names in a project from an older version) but it was never reset, so it popped up in every update script.
|
Fix |
Templates 4.2 |
Templates 4.2 |
08062014 |
06-Aug-2014 |
The Framework validators of entity framework v5 and v6 weren't copied to the right folders and therefore outdated versions were shipped with the installer. |
Fix |
Designer 4.2 |
Designer Core 4.2 |
August 1st, 2014 |
01-Aug-2014 |
Renaming an element in the catalog explorer didn't invoke the name length limit set for the database used, making it possible to specify a name longer than the name length limit of the database. |
Fix |
Designer 4.2 |
Designer Core 4.2 |
July 30th, 2014 |
30-Jul-2014 |
Catalog refresher: it could be that if a field became part of the PK, the refresher crashed with an exception that an enumerator was changed due to the fact an event was raised. |