Adopt the WAQS framework into EF source code

WAQS framework is a layer of abstraction over the Entity Framework

WAQS is addressing many of the painful scenarios under EF, with a great design and productivity.

http://www.dailymotion.com/video/xuc1jb_waqs-application-scaffolding_tech

Starting with Entity Framework 5, Enum property is now supported (and it's a great feature !).

It would be nice if EF support the HasFlag method. For example :

context.ScheduledTasks.Where(st => st.Days.HasFlag(DayOfWeek.Sunday));

won't work (LINQ to Entities does not recognize the method 'Boolean HasFlag(System.Enum)' method, and this method cannot be translated into a store expression.)

I know that the following query will work :

fooContext.ScheduledTasks.Where(st => (st.Days & DayOfWeek.Sunday) == DayOfWeek.Sunday);

but it's more difficult to read, especially when there is a lot of condition.

Could you support the HasFlag method ?

Thanks,

Because in EF6 the ObjectContext class is being moved into the EntityFramework assembly, existing code will treat it separately from the "old" ObjectContext in the System.Data.Entity assembly.

I use EF CodeFirst in a mixed MVC / WebForms(DynamicData) application.

Either bring out new versions of EntityDataSource and DynamicData for EF6 or provide a way from going from a EF4/5 ObjectContext to an EF6 one.

Especially for migration projects it would be useful to allow entities to be saved with predefined identity values.

Until now you have to use ADO.NET to do this.
SET IDENTITY_INSERT TableName ON
INSERT INTO TableName (IdColumn, Column1)
VALUES (234, 'Value')

I would like to tell the DbContext to use this feature when saving new entities.

There is no way in EF to do a true native LIKE with wildcards (% and _). "Contains" limits you to %value%. Would like to be able to specify the wildcards within the LIKE myself. For example:

select * from table where name like '%a_b_c%'

At the moment there is no way to do this unless you use SqlQuery/ESQL.

Other options, such as INSTR are not desirable alternatives.

I would like to see the T-SQL MERGE statement supported. For multi threading situations it really would be useful.

I think there would be nice idea if you give method to delete collection. Without using foreach statement.

Now:
foreach(var item in collection)
{
db.Customers.Remove(item);
}
db.SaveChanges();

and should be simply

db.Delete(collection);
db.SaveChanges();

I would like to see update-able views. This is available in Telerik ORM, and I have found it very helpful in situations where I initially assumed a grid would only need to display read only data, but was months later asked to allow editing.

There are other ways to do this of course, but they require recoding. This would make certain maintenance tasks easy.

System.Data.dll -- which is fundamental to EF -- is not available inside Windows Store Apps. Thus development of Windows Store apps is two steps back of where WPF and Silverlight development have been.

scalar function is used usually some custom function to retrieve some only one value.
eg.custom ID not Guid

ADO.Net supports bulk insert for big amount of data. With the help of this library
http://archive.msdn.microsoft.com/LinqEntityDataReader
It is possible to do Bulk inserts with entities. But it would be nice if there would be a integrated approach.

Currently if you have something like

select new { Year = c.DateEntered.Year }

the generated sql uses C1 for the column name. I would find it very useful if the used Year.

When creating the edmx (Database First) within Visual Studio, there should be a checkbox to tell the code generators to create a separate library that contains the entities selected from the database. These can be used as domain objects/models across all layers in the application.

Currently in EF5, you have to cobble together some hack to separate the POCO's - delete xml entries in the *.csproj and do other dangerous steps just for separation.

EF6 should have the hooks for configuration by users within Visual Studio.

That's the one thing NHibernate has over EF - separate POCO's

Thanks!

If you have a class like

public class CustomerAddress
{
public virtual Customer Customer { get; set; }
public virtual Address Address { get; set; }
public virtual string AddressType { get; set; }
public virtual DateTime ModifiedDate { get; set; }
}

you should be able to create a composite id like this

HasKey(a => new { a.Customer, a.Address });

without defining CustomerId and AddressId properties

I am creating a Database with the Model First SQL Script Generation. Then later when I need to Update the Model I don't want to delete all tables and content, I want to generate an update Script.

Its possible in EF4 with an Tool:
http://visualstudiogallery.msdn.microsoft.com/df3541c3-d833-4b65-b942-989e7ec74c87/

but in EF5 there is atm no possibility to update the Model with "Model first".

Idea: perhaps try to include the SQL-Schema Comparer in EF.

can create query on each database with query string that schema not defined for entity framework and auto map to object

Provide an access to the code-first metadata mapping.
The mapping is already described. Why not to provide a public access to a table name, schema, class property to table column mapping.
It will allow to build advanced SQL queries using Database.SqlQuery when performance is is needed. For example - bulk inserts in one query. Or other queries that don't require object state tracking. Currently you need to hard code schema, table and column names in a string, why not provide a way to build a query using defined mapping metadata?

Be able to map subclasses based on whether a column is null or not. This works in the EDMX, but not Code First