DAT 304: Next Generation Data Access in ADO.NET vNext
Pablo is giving us a talk about what the next changes and solutions in ADO.NET 3.x.
· Key drivers for them are providing an ORM tool without tossing out ADO.NET fundamentals.
· Most applications are data centric apps, Microsoft places high priority in preserving investments
· Two-fold strategy: Widen the stack with the conceptual model and adding an object layer on top of the ADO.NET primatitives
· Key themes for ADO.NET 3.x: conceptual data models; better integration with .NET and better integration with languages via LINQ.
· Showed a demo of DataDude and LINQ, Started with and Entity Diagram, a design surface in Studio 2005. Saving the ED generates a mapping layer via CLR classes. Can now use that an object binding. Showed a LINQ over DLINQ to do a filtering query. Showed one-line data persistence.
· Went into a discussion of Schemas (database, not XSD). Schemas can be less than ideal for an application and client views a logical separation level. Client-side instance that become updatable and statically verifiable.
· Views are surfaced as an ADO.NET provider and how to worked with Mapped View using Map* as we would Sql* or OleDb* data access classes. Security isn’t done at the mapped view level, but instead at the base table level. Baby steps, I guess.
· Talked about the Entity Data Model as structured records with keys and structural inheritance and it becomes and executable. Entities look to become the primary mediation object.
· Introduced that there would be Entity SQL for query for entity data and entity meta data. Stressed that this gives us a very high degree of database independence. Join syntax will be done with a WHER NAVIGATE function in the moment. Bit look a bit primitive yet, but should be very powerful.
· Talked about Object Services using ObjectContext vs. a provider and a Query. This will use either Entity SQL or LINQ. This looks pretty cool and like it should generate less net code.
· ObjectContext has a generic persistence method that does optimistic concurrency within a TranscationScope.
· Pablo then dug into LINQ. At this point I decided to exit.