Created Unassigned: Migrations :: invalid migration created when playing with...
This may be related to https://entityframework.codeplex.com/workitem/1310Basically when I create a particular 3 step migration I get an error, but if I collapse steps 1 and 2 into single migration, it...
View ArticleEdited Unassigned: Migrations :: invalid migration created when playing with...
This may be related to https://entityframework.codeplex.com/workitem/1310Basically when I create a particular 3 step migration I get an error, but if I collapse steps 1 and 2 into single migration, it...
View ArticleEdited Unassigned: Migrations :: invalid migration created when playing with...
This may be related to https://entityframework.codeplex.com/workitem/1310Basically when I create a particular 3 step migration I get an error, but if I collapse steps 1 and 2 into single migration, it...
View ArticleEdited Unassigned: Migrations :: invalid migration created when playing with...
This may be related to https://entityframework.codeplex.com/workitem/1310Basically when I create a particular 3 step migration I get an error, but if I collapse steps 1 and 2 into single migration, it...
View ArticleCommented Issue: Using the designer to make a DbSet property non-public...
You can choose to make a DbSet property non-public, but once this happens the automatic initialization of the property by DbContext does not happen. (This is because we choose not to mess with...
View ArticleEdited Issue: Using the designer to make a DbSet property non-public results...
You can choose to make a DbSet property non-public, but once this happens the automatic initialization of the property by DbContext does not happen. (This is because we choose not to mess with...
View ArticleEdited Issue: Designer Model First :: script that we generate yields errors...
When generating database script from model, we use the following:USE [MyDatabaseName];which throws the following error:USE statement is not supported to switch between databases. Use a new connection...
View ArticleCreated Unassigned: Stored Procs :: error during scaffold migration when...
Repro - create the following model:``` public abstract class Weapon{ public int Id { get; set; }// 1 - 1 self reference public virtual Weapon SynergyWith { get; set; }} public class HeavyWeapon :...
View ArticleEdited Issue: Query: Inefficient SQL generated for Any() [192]
Repro Steps: 1. Execute an Entity Framework query that uses Any() to check for the existence or absence of a matching record. 2. Check the executed SQL.When using the Any() method on Entity Framework...
View ArticleEdited Issue: Query: Inefficient SQL generated for Any() [192]
Repro Steps: 1. Execute an Entity Framework query that uses Any() to check for the existence or absence of a matching record. 2. Check the executed SQL.When using the Any() method on Entity Framework...
View ArticleClosed Issue: Code first sproc mapping: revisit RowsAffected parameter...
(Note for triage: we discussed this with Andrew and we agreed we should try to fix it for EF6 as the current behavior is not consistent nor the most helpful but changing it later would be a breaking...
View ArticleCreated Unassigned: Stored Procs :: clean up stored proc specification [1320]
Feature specification is out of date. We should update it with latest changes. Specifically: - Name of stored procedure for Many-Many mapping ,- @RowsAffected is no longer added as output parameter by...
View ArticleEdited Unassigned: Stored Procs :: clean up stored proc documentation [1320]
Feature specification ( http://entityframework.codeplex.com/wikipage?title=Code%20First%20Insert%2fUpdate%2fDelete%20Stored%20Procedure%20Mapping )is out of date. We should update it with latest...
View ArticleUpdated Wiki: Code First Insert/Update/Delete Stored Procedure Mapping
In previous versions of EF it was only possible to map Code First entities directly to tables. It is fairly easy to use SqlQuery to select data using stored procedures but there was no feasible way to...
View ArticleEdited Task: Implement connection resiliency name changes [1273]
As part of our API review for connection resiliency we identified a few names that we wanted to change. The changes are:1. IExecutionStrategy to IDbExecutionStrategy2. NonRetryingExecutionStrategy to...
View ArticleCreated Unassigned: SqlCePropertyMaxLengthConvention should be updated to...
the PropertyMaxLengthConvention was updated in a recent change to improve extensibility, but the SqlCe version of that convention was not similarly updated. The Sql Ce convention should be updated to...
View ArticleCommented Task: Designer: Consider scenarios where both EF5 and EF6 are...
It is possible for a project to reference both EF4/EF5 (SDE.dll) and EF6. We should consider either supporting these scenarios in the designer, ensuring the latest version is always used when possible...
View ArticleSource code checked in, #6bbde07a77b8c2b563e3046421d44ab21829d956
Changing DbExecutionStrategy to reset state instead of throwing Workitem: 1274
View ArticleCommented Task: Make sure VS integration works correctly with EF vNext [1150]
Various things make use of EF in VS--for example MVC scaffolding, the EF designer, etc. These may expect exactly EF6 to be used, when in fact it may be that the version of EF after EF6 is being used....
View ArticleEdited Task: Change DbExecutionStrategy to reset state instead of throwing...
Instead of setting a flag and throwing when calling execute twice we should just reset the state. It’s possible that throwing will help users identify that they are using resolvers incorrectly, but we...
View Article