InfoQ Homepage Data Access Content on InfoQ
-
LINQ-to-Twitter, Another LINQ Provider
Mehfuz Hossain, a Microsoft MVP, has created a LINQ-to-Twitter provider. This is yet another example demonstrating that LINQ is not a framework to access just data in a database but it can be used with all sorts of objects, including tweets.
-
Introducing ADO.NET Data Services 1.5
The first version ADO.NET Data Services was originally slipped into a service pack for .NET 3.5. Finding that it did not quite meet customer expectations, another version is on its way.
-
Interview: Erik Meijer on LINQ
In this interview made during QCon SF 2008, Erik Meijer talks about less known LINQ features, like the ability to do meta programming or the fact that LINQ works against any data collection that implements the sequence operators. Meijer also talks about the differences between functional languages and objectual ones, asynchronous computation, and the evolution of languages.
-
Moneta: An Interface to Key-Value Stores like Tokyo Cabinet, Memcache
Key-value stores are a viable alternative to relational databases. We take a look at Tokyo Cabinet and how different key-value stores can be unified behind a common interface with Moneta.
-
Article: Blaze Data Services or LiveCycle Data Services?
This article, by Ryan Knight, compares two similar products: Adobe’s LiveCycle Data Services (LCDS) and Open Source Blaze Data Services. The comparison is necessary to know the differences between the two products in order to choose the right one for a certain situation.
-
Fluent NHibernate Has a Wiki
Fluent NHibernate is an alternative to using XML mappings in NHibernate. Fluent NHibernate is using a fluent interface allowing you to define mappings in code instead of XML. Some people in the community have complained about the lack of documentation for Fluent NHibernate and as a response James Gregory recently announced the official Wiki for Fluent NHibernate.
-
Presentation: CouchDB and Me
In this talk from RubyFringe, Damien Katz explains what drove him to create CouchDB, why he chose Erlang, how it ended up as an Apache project and much more.
-
Two Type-Safe Criteria API Proposals for JPA 2.0
One of the most significant new features in the forthcoming Java Persistence API 2.0 specification is a type-safe criteria-based query API. There are two alternative proposals under consideration by the JSR-317 Expert Group and the group is seeking feedback from the wider development community.
-
New Entity Framework Providers: OpenLink and Firebird
OpenLink and Firebird have been added to the list of supporters of the Entity Framework by releasing their ADO.NET 3.5 providers.
-
Eventually Consistent, Revisited
Building reliable distributed systems at a worldwide scale demands trade-offs between consistency and availability. Last month, Amazon’s CTO Werner Vogels posted an article describing approaches to tolerate eventual data consistency in large-scale distributed systems.
-
Article: Performance Anti-Patterns in Database-Driven Applications
In this article, Alois Reitbauer, a Performance Architect for dynaTrace Software, specifies several architectural anti-patterns which can downgrade an application’s performance. Knowing those anti-patterns and proactively designing the application to avoid them will keep away certain snags that can impact application’s performance.
-
IBM’s Data Server Provider for .NET Supports the Entity Framework
IBM has released the production version of its Data Server Provider for .NET including support for Microsoft’s Entity Framework allowing its users to create EDM schemas, and to execute EntitySQL and LINQ statements.
-
LINQ to SQL, The Next Step
Despite the numerous problems with Microsoft ORMs and the plethora of alternatives such as LLBLGen, nHibernate, and OpenAccess, many developers are forced to use Microsoft tech because that is why their company or customer wants. And between the two offerings, it seems most developers believe that Entity Framework is not a viable option. So what are they do to?
-
Does LINQ-to-Entities really return different results depending on previous queries?
In a recent blog post Stu Smith claimed that “LINQ-to-Entities will return different results depending on what previous queries you’ve executed!”. If true, this would make using Entity Framework much harder than necessary to use. We talked to Elisa Flasko of the ADO.NET Team to find out what’s really going on.
-
Working Around Entity Framework's Large Data Model Issues
The Entity Framework doesn't support data models with much more than 50 to 100 entities. But since companies typically run everything from one central database, several hundred tables are the norm. Microsoft's ADO.NET team is presenting an article on Working With Large Models In Entity Framework, a list of issues and work-arounds for EF users.