Group items tagged

"ORM users have grown accustomed to thinking in terms of .NET and LINQ, forgetting the specifics of particular databases, differences in their functionality and effectiveness of certain SQL-constructions. In this article, we shall briefly discuss some of the problems that the user may face in the process of developing an application for Entity Framework (EF), which is meant to interact with Oracle, MySQL, PostgreSQL or SQLite rather than Microsoft SQL Server. I hope this will be useful both for users who create an EF-application for these databases for the first time as well as for those who create an application that must support interaction with multiple databases, i.e., SQL Server and Oracle. As examples of implementing EF-providers for databases other than SQL Server, we shall use Devart ADO.NET providers."

"PetaPoco is a tiny, fast, single-file micro-ORM for .NET and Mono. Like Massive it's a single file that you easily add to any project Unlike Massive it works with strongly typed POCO's Like Massive, it now also supports dynamic Expandos too - read more Like ActiveRecord, it supports a close relationship between object and database table Like SubSonic, it supports generation of poco classes with T4 templates Like Dapper, it's fast because it uses dynamic method generation (MSIL) to assign column values to properties"

"Something I've been looking at adding to AutoMapper was the idea of doing automatic query projection in the Select query projection in LINQ statements. One downside of AutoMapper is that projection from domain objects still forces the entire domain object to be queried and loaded. For a lot of read-only scenarios, loading up a tracked, persistent entity is a bit of a waste. And unless you're doing CQRS with read-specific tables, you're doing projection somehow from the write tables."

"A few months ago, Jimmy Bogard, author of the excellent AutoMapper wrote a great article about Autoprojecting LINQ queries. Now that Jimmy has done all the hard expression tree work, this article extends his example to include caching and simple flattening capabilities and goes on to show it in use in a simple EF 4.1 Code First application."