Compiler Plugins Can Handle Nested Languages: AST-Level Expansion of LINQ Queries for Java

García, Miguel

doi:10.1007/978-3-642-14681-7_3

Cited by 1 publication

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To simplify the formulation of valuation functions, a query is regarded as a sequence S of body clauses Q, with query continuations desugared into subqueries [15].…”

Section: Discussionmentioning

confidence: 99%

“…However, LINQ functionality results from the interplay of several technologies, the first one covering compile-time translation from LINQ textual syntax embedded in languages such as C# and VB.NET into Standard Query Operators (SQO), which are comparable to the operators in collection libraries of programming languages supporting closures. For example [15], the textual syntax from x in foo let y = f(x) select h(x, y) actually stands for the following code: foo.Select(x => new { x, y = f(x) }).Select(t0 => h(t0.x, t0.y)). All we need to know about these expressions is that LINQ renames the well-known map, filter, and flatMap into Select, Where, and SelectMany.…”

Section: Microsoft Linqmentioning

confidence: 99%

“…The input AST for a LINQ query already has query continuations inlined [15], i.e., subqueries were recast from the idiosyncratic "from x1 in e1 qclauses into x2 qcont " // from str in strs let chrArr = str. ToCharArray() // from ch in chrArray // orderby ch select ch val res9 = for ( ( str , chrArr, ch ) <− ( ( for ( str <− strs; val chrArr = str.…”

Section: Comprehensions In Linq and Scalamentioning

confidence: 99%

See 2 more Smart Citations

Extending Scala with Database Query Capability.

García¹,

Izmaylova²,

Schupp³

2010

JOT

Self Cite

View full text Add to dashboard Cite

The integration of database and programming languages is difficult due to the different data models and type systems prevalent in each field. We present a solution where the developer may express queries encompassing program and database data. The notation used for queries is based on comprehensions, a declarative style that does not impose any specific execution strategy. In our approach, the type safety of languageintegrated queries is analyzed at compile-time, followed by a translation that optimizes for database evaluation. We show the translation total and semantics preserving, and introduce a language-independent classification. According to this classification, our approach compares favorably with Microsoft's LINQ, today's best-known representative. We provide an implementation in terms of Scala compiler plugins, accepting two notations for queries: LINQ and the native Scala syntax for comprehensions. The prototype relies on Ferry, a query language that already supports comprehensions yet targets SQL:1999. The reported techniques pave the way for further progress in bridging the programming and the database worlds.

show abstract

“…To simplify the formulation of valuation functions, a query is regarded as a sequence S of body clauses Q, with query continuations desugared into subqueries [15].…”

Section: Discussionmentioning

confidence: 99%

Section: Microsoft Linqmentioning

confidence: 99%

Section: Comprehensions In Linq and Scalamentioning

confidence: 99%

See 1 more Smart Citation