Paul Gielens:ThoughtsService

another Endpoint to my thoughts

News

Syndication

  		•

Ads


Favorites

Projects

ADO.NET vNext Future Directions 5

Also see the first, second, third and fourth part of this series of posts on the next generation data access for the .NET platform.

Entity SQL currently does not include support for the Data Manipulation Language (update, delete, insert into functions) and according to Daniel Simmons possibly not even for the first release of the Entity Framework (discussion). Updates to entities must be made through the object services layer by calling SaveChanges on an ObjectContext instance.

The team is currently actively working on support for stored-procedures (discussion).

CommandBehavior.SequentialAccess is here to stay (discussion). You'd want to use Query<T> anyway.

Table with self-references will be supported in future releases (discussion).

Abstract entities will be supported in future releases (discussion).

XML data type will be supported in future releases (discussion).

Posted: Sep 19 2006, 12:19 PM by p.gielens | with 2 comment(s)
Filed under:

Comments

Alex James said:

Hey Paul,

Given your obvious interest in ADO.NET Entities, does this mean you are putting less into NEO now?

BTW, I really like the elegance of the schema language for NEO.

Alex

# September 28, 2006 12:07 AM

p.gielens said:

To be honest I haven't been able to use Neo2005 on any of my new projects. This doesn't mean I'll abandon my work, but checking-in alpha bits into the Neo repository could affect current users. Unfortunately I wont be able to commit to any open-source project in the next few months. Although, I will reserve some spare time during the holidays to finalize 2.0 support.

# September 28, 2006 4:02 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)