Abstract

We demonstrate an efficient LINQ to SQL provider and its significant impact on the runtime performance of LINQ programs that process large data volumes. This alternative provider is based on Ferry, compilation technology that lets relational database systems participate in the evaluation of first-order functional programs over nested, ordered data structures. The Ferry-based provider seamlessly hooks into the.NET LINQ framework and generates SQL code that strictly adheres to the semantics of the LINQ data model. Ferry comes with strong code size guarantees and complete support for the LINQ Standard Query Operator family, enabling a truly interactive and compelling LINQ demonstration. A variety of inspection holes may be opened to learn about the internals of the Ferry-based LINQ to SQL provider. 1. SINGLE-LINE CHANGE—BIG IMPACT “Will we be able to defeat the Bs this time? ” This can be a pressing question if you are the coach of team A. You peer at the large players table of this year’s Basketball season (Table 1), featuring the player data of all teams. A list of the individual team rosters and a classification of a team’s players by their position— center, forward, or guard—would be more helpful now. You reach for your laptop computer to start the C # development environment. A brief program, formulated using the.NET Framework’s Language Integrated Query facility (LINQ), will do the job. You quickly create a data context, a LINQ abstraction that represents (1) a connection to a relational database back-end as well as (2) selected tables hosted by this back-end (including table players). players team name pos eff

Citations