mark

My feedback

  1. 153 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    mark commented  · 

    This is important.

    A complication that needs to be solved is how to synchronize the in-memory entities with store entities. This should be possible using the OUTPUT clause in SQL Server.

    For DELETE, output the keys for the deleted rows and update the in-memory entities.
    For UPDATE, output the keys and written columns.
    For INSERT, output everything.

    There are two variations of bulk DML: DML by query (e.g. insert ... select) or client-provided data (e.g. SqlBulkCopy). In the latter case it might be necessary to write to a temp table first using SqlBulkCopy. After doing that the OUTPUT clause can be used in the actual DML statement.

    One should be able to write:

    someTable.Insert(myStoreQuery);

    as well as

    someTable.Insert(inMemoryCollection);

  2. 192 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    mark supported this idea  · 
  3. 408 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    mark supported this idea  · 
  4. 15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    mark commented  · 

    Entity Framework should support using very common BCL features such as DateTime.Date in LINQ queries. Right now this requires the use of the special TruncateTime function.

    The problems are as follows:
    - This feels unnatural.
    - It also is a problem when migrating from LINQ to SQL which did support DateTime.Date.
    - It makes moving code across LINQ providers harder (e.g. move a piece of code from LINQ to objects to EF in order to remote it to the SQL Server)

    Other common features should be supported as well. For example DateTime.Year or TimeSpan stuff.

    Some are already supported such as Guid.NewGuid. That's good.

    mark supported this idea  · 

Feedback and Knowledge Base