| Fix |
Templates 4.0 |
Templates 4.0 |
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.0 |
Runtime Libraries 4.0 |
09032014 |
03-Sep-2014 |
OracleDQE / Linq: the function mapping for the DateTime.Add* functions used INTERVAL which didn't work for parameterized queries. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
06042014 |
04-Jun-2014 |
Linq, VB.NET: if a string comparison was done using an operator other than = or <>, (so >, < etc.) the linq provider would create query which would never return a value as the CompareString method mapping was wrong. |
| Fix |
Designer 4.0 |
Designer Core 4.0 |
May 5th, 2014 |
05-May-2014 |
When only TVF calls were present in the catalog, they were ignored when the project was persisted. |
| Fix |
Templates 4.0 |
Templates 4.0 |
05022014 |
02-May-2014 |
LLBLGen Pro Runtime Framework: Backport of v4.1 fix: Postgresql: Fixed issue with stored procedure name quoting for case insensitive stored procs as workaround for an issue in npgsql |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
01132014 |
13-Jan-2014 |
Postgresql, linq : if an IIF function was used in a projection and a null value was returned as one of the two possible return values, the query could fail due to the fact the null value was passed as a varchar parameter because no type information is known at that point. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
12112013 |
11-Dec-2013 |
Queryspec: a having clause with a function mapping wasn't properly prepared: the functionmapping wasn't converted into handleable elements |
| Fix |
Designer 4.0 |
Designer GUI 4.0 |
November 26th, 2013 |
26-Nov-2013 |
When the catalog details viewer was closed with the context menu, the viewer stayed hidden. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
11082013 |
08-Nov-2013 |
If invalid old-style paging variables were specified (0 for pagenumber and non-zero for pagesize, or non-zero for pagenumber and 0 for pagesize), it could be the pagesize was still considered as the maximum number of rows to return over the specified maximum limit. |
| Change |
Designer 4.0 |
Designer Core 4.0 |
October 21st, 2013 |
21-Oct-2013 |
VS.NET Extension now also works in VS.NET 2013. Installer has been adjusted to properly register it with 2013 as well. |
| Fix |
Designer 4.0 |
Designer Core 4.0 |
September 30th, 2013 |
30-Sep-2013 |
In some cases it could be the update/delete cascade rules in a relationship in the model weren't synced with the FK update/delete cascade rules after a refresh, causing problems the next time a refresh was issued, if the rule values in the relationship are different from the FK ones: it would trigger a mandatory update DDL SQL script export. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
09232013 |
23-Sep-2013 |
In an edge case it could be an IConvertible implementing object wasn't converted to char/string properly using the CharStringConverter type converter. |
| Fix |
Drivers 4.0 |
Drivers 4.0 |
09230213 |
23-Sep-2013 |
SQL Server driver: if a database had multiple schemas and one had a synonym it could be the schema retrieval would crash in the designer because a table was added twice. |
| Fix |
Templates 4.0 |
Templates 4.0 |
09232013 |
23-Sep-2013 |
Oracle DDL SQL scripts: when an FK On Delete rule was set to NoAction, the DDL SQL alter table statement contained an ON DELETE NO ACTION statement which is something Oracle throws an error on as NO ACTION Is the default and ON DELETE therefore should be omitted. |
| Fix |
Drivers 4.0 |
Drivers 4.0 |
09202013 |
20-Sep-2013 |
Oracle drivers: RAW was always seen as a type with 2GB length. |
| Fix |
Designer 4.0 |
Designer GUI 4.0 |
September 20th, 2013 |
20-Sep-2013 |
In the normal relationship editor, changing the update/delete rules selectors would reset the names of the navigators |
| Fix |
Designer 4.0 |
Designer Core 4.0 |
September 2nd, 2013 |
02-Sep-2013 |
When a relationship's cascade rules were updated, the backing FK constraint wasn't updated due to a change we made on July 17th, which was too strict. FK constraints which are not an inheritance FK are updated always with the rules of the relationship creating them (as designed), FK constraints for inheritance have their rules set once, when they're created. |
| Addition |
Templates 4.0 |
Tasks 4.0 |
08212013 |
21-Aug-2013 |
Entity Framework 5: A new setting for fields has been added, ForcedStoreGeneratedPatternValue, which can have the values 'None' (default), 'Identity' or 'Computed', and which forces the code generator to use the selected value for StoreGeneratedPattern. None, the default, will leave the StoreGeneratedPattern specification to the code generator.
|
| Addition |
Templates 4.0 |
Tasks 4.0 |
08192013 |
19-Aug-2013 |
Entity Framework 5: Added a project setting, called 'DontUseStrongSpatialTypes' which is by default set to true. It's recommended to leave this as true. It'll cause the EDMX include template to emit an annotation in the CSDL definition element so geometry/geography types work. |
| Change |
Task Performers 4.0 |
Code generator 4.0 |
08012013 |
01-Aug-2013 |
TDL statements ParameterSize/Precision/Scale emitted the Length/precision/scale of the parameter in the stored procedure call, but it should emit the values of the mapped target procedure, as the values are used to create the DbParameter. Normally this is not noticeable, only in the case where the project was converted from v2 and the precision/scale/length values were reset to 0 as they're not used in general for db element creation. |
| Change |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
07312013 |
31-Jul-2013 |
Firebird DQE, sequence triggers: If CompatibilityLevel is set to 2.0 (default), no longer is GEN_ID(sequence, 0) passed as temp value for a sequenced field in an INSERT query when FirebirdTriggerSequences is set to true, but NULL, as GEN_ID(sequence, 0) might fool some trigger code a value has been set while NULL is more accepted as a value indicating the sequenced field has not yet been set to a value, so triggers will more likely be going to set the sequenced field to a new sequence value. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
07302013 |
30-Jul-2013 |
Entity collection's AddRange method didn't raise the Reset event, so a bound view never raised the Reset event either. |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
07252013 |
25-Jul-2013 |
A field of type DateTimeOffset wasn't properly converted to/from XML |
| Fix |
Runtime Libraries 4.0 |
Runtime Libraries 4.0 |
07222013 |
22-Jul-2013 |
Inheritance, QuerySpec: in an edge case it could be that the query for a nested query in a projection of a dynamic query crashed the SQL production engine because the correlated over resulting predicate added a hierarchy relationship to the nested query's FROM clause. |
| Fix |
Designer 4.0 |
Designer Core 4.0 |
July 18th, 2013 |
18-Jul-2013 |
Altering a value for a default in the settings would save the settings as 'OutputSettingValues' instead of 'Defaults'. While this has no impact on the functioning of the designer, it could lead to merge issues with source control in some edge cases. |