In the world of database architecture, the need to dynamically create complex objects conflicts with the demand for subsecond response time. Oracle's answer to this dilemma is the materialized view.

Twice in the past couple of months I’ve gotten tripped up by the same data issue when using LINQ to Entities in the .NET framework. I create a simple view in my database which performs some ...