home / Change Log Browser

Change-logs for the LLBLGen Pro system

Below you are able to browse through the changelogs of all elements of the LLBLGen Pro system for various versions. There's also an easy to use search function for you available (shown when applicable) which allows you to search through all the change log entries using Full text search queries.

Application

LLBLGen Pro 4.2

All changes logged for:

  • Application: LLBLGen Pro 4.2


Number of logged changes found: 167

Change type Package Component For build Logged on Change text
Fix Templates 4.2 Templates 4.2 09282015 28-Sep-2015 Entity Framework, Code First: In a TPEH hierarchy, if the entities were mapped onto a table with a different name than the entity, the table directive wouldn't be emitted, causing queries to fail.
Fix Drivers 4.2 Drivers 4.2 09252015 25-Sep-2015 PostgreSQL driver, npgsql 3.0.2+: The type 'geometry' was reported as varchar by previous iterations of the driver, however on npgsql v3 this doesn't work anymore. It now falls back to Text.
Fix Drivers 4.2 Drivers 4.2 09252015 25-Sep-2015 PostgreSQL driver, npgsql 3.0.2+: after a refresh, if the driver's mapping tables were read by the designer, e.g. when an entity field's edited in the mapping editor, the designer threw an NRE due to missing type name information in the updated mapping tables for npgsql 3
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 09142015 14-Sep-2015 Linq: Additional correction on Nested query related fix introduced on August 27th, 2015: it covers now a missed edge-case.
Fix Drivers 4.2 Drivers 4.2 09042015 04-Sep-2015 PostgreSQL driver, npgsql v3.x: due to a change in Npgsql v3 in how values are retrieved from a postgresql server, the query we used to obtain materialized views in a postgresql schema failed with an exception in Npgsql v3 due to an unsupported type. A change in the query used in our driver works around that.
Change Drivers 4.2 Drivers 4.2 08272015 27-Aug-2015 PostgreSQL driver: v3 maps Time and Timestamp with Timezone to different types. Mapping tables are adjusted when v3 of npgsql is used.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 08272015 27-Aug-2015 Linq: when a nested query with a custom projection contained an m:n relationship and multiple navigation hops, the query failed as the engine failed to tie the nested query to the outer query.
Change Drivers 4.2 Drivers 4.2 08262015 26-Aug-2015 PostgreSQL driver: 'protocol' has been removed as it's not used in v2 of npgsql and v3 gives an error when protocol is used in the connection string.
Change Drivers 4.2 Drivers 4.2 08262015 26-Aug-2015 PostgreSQL driver: v3 of Npgsql doesn't support 'encoding' nor 'SSL' connection string arguments anymore. These were obsolete anyway, so we removed them. Driver works with v2 and v3 now.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 08212015 21-Aug-2015 MySQL, Stored Procs, Catalog name overwriting: overwriting catalog names in stored proc calls didn't always work.
Fix Drivers 4.2 Drivers 4.2 08142015 14-Aug-2015 SQL Server driver, Synonyms: For a synonym, fields with type Image / Text / NText and NChar(n) / NVarchar(n), with n < 8000, got their max lengths wrong (either 16 where 2GB should have been reported, and length in bytes instead of length in characters).
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 08032015 03-Aug-2015 Linq / QuerySpec: If an entity query with a subtype as element type was converted to a derived table by the query engine, the engine sometimes didn't append a type filter, causing wrong results to be returned. Example: var c = (from d in metaData.Marketing join m in metaData.Manager on d.DepartmentId equals m.WorksForDepartmentId select d).Count();
Fix Designer 4.2 Designer Core 4.2 August 2nd, 2015 02-Aug-2015 Fix for validator for duplicate navigator fix as an essential line of code was not present in the final build.
Addition Designer 4.2 Designer Core 4.2 July 27th, 2015 29-Jul-2015 Added validation rule which picks up duplicate navigator names, a situation which could occur in an edge case when a subtype inherited a navigator from a supertype and the relationship was reverse engineered after the hierarchy was already present (through a 3rd entity, adding the navigators) or when the hierarchy was created after the relationships were already present.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 07292015 29-Jul-2015 Linq: The fix introduced on 12-dec-2014 created a bug where when multiple entities were present in the projection (e.g. select new {Customer = c, Order=0}) it would fail in some occasions because of indexing issues in the projector.
Fix Designer 4.2 Designer Core 4.2 July 24th, 2015 24-Jul-2015 CatalogRefresher: Logging activity went wrong when two or more TVFs returned the exact same element.
Addition Templates 4.2 Tasks 4.2 07212015 21-Jul-2015 Added .NET 4.6 as a platform and enabled .NET 4.6 for various frameworks / tasks
Change Designer 4.2 Designer Core 4.2 July 21st, 2015 21-Jul-2015 The designer and related assemblies are now compiled using Roslyn C# compiler
Change Runtime Libraries 4.2 Runtime Libraries 4.2 07212015 21-Jul-2015 Runtimes are now compiled using Roslyn C# compiler.
Change Runtime Libraries 4.2 Runtime Libraries 4.2 07212015 21-Jul-2015 Linq, Async: Change in async method info retrievers so they work when compiled using Roslyn
Fix Templates 4.2 Templates 4.2 07172015 17-Jul-2015 Entity Framework, Code First: the FK fields in an m:n mapping were in the wrong order (left key should be right key and vice versa)
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 07082015 08-Jul-2015 QuerySpec: In some cases a correlation predicate wasn't properly wrapped as a correlation predicate which could lead to problems when the correlation predicate was used on a nested query with inheritance inside exists (and related operators) queries.
Fix Runtime Libraries 4.2 Runtime Libraries 4.2 06192015 19-Jun-2015 Oracle, ODP.NET: In ODP.NET, passing an array of elements in a parameter using direct odp.net targeting code, in combination of an ActionQuery, could lead to problems in the error reporting if an exception occurred because odp.net sets the DbType of the parameter to the element type inside the array that's the value of the parameter, not to 'array', causing a cast exception.
Addition Task Performers 4.2 Code generator 4.2 09062015 09-Jun-2015 A preference setting, UseCurrentCultureForNameSorting, default true, has been added to solve the following: Ordering of elements by Name used the current culture set by the OS. By default this is still the case. Setting the preference UseCurrentCultureForNameSorting to false will make the designer and code generator use the invariant culture for all name ordering, be it in file persist, ordering of elements in the UI and in the code generator.
Addition Templates 4.2 Templates 4.2 06092015 09-Jun-2015 A preference setting, UseCurrentCultureForNameSorting, default true, has been added to solve the following: Ordering of elements by Name used the current culture set by the OS. By default this is still the case. Setting the preference UseCurrentCultureForNameSorting to false will make the designer and code generator use the invariant culture for all name ordering, be it in file persist, ordering of elements in the UI and in the code generator.