Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Eclipse DemoCamps November 2008/Hamburg/Session Abstracts"

(Rethinking the Architecture of Java ORM in terms of LINQ)
(Rethinking the Architecture of Java ORM in terms of LINQ)
Line 4: Line 4:
 
The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation.  Regarding the outline below, the first two items have already been reported in [1], the remaining are new.
 
The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation.  Regarding the outline below, the first two items have already been reported in [1], the remaining are new.
  
a)  LINQ set of technologies distilled. Architectural differences between JPA ORM and ADO.NET Entity Framework. Benchmarks for queries on large ORMed Ecore models
 
  
b)  LINQ-favored approach to runtime translation into the query language of the target persistent store
+
== Outline ==
  
c)  Products and prototypes in the Java space aiming at LINQ functionality. We showcase the approach adopted by JaQue, which aims to adopt bytecode inspection to translate LINQ statements into the persistent store's native query language
+
# LINQ set of technologies distilled. Architectural differences between JPA ORM and ADO.NET Entity Framework. Benchmarks for queries on large ORMed Ecore models
 
+
# LINQ-favored approach to runtime translation into the query language of the target persistent store
d)  the venue plan to follow for future work, building upon technologies developed in the projects [Pathfinder http://www.pathfinder-xquery.org]  and [Ferry http://www-db.informatik.uni-tuebingen.de/research/ferry], both being developed at U Tübingen.
+
# Products and prototypes in the Java space aiming at LINQ functionality. We showcase the approach adopted by JaQue, which aims to adopt bytecode inspection to translate LINQ statements into the persistent store's native query language
 +
# the venue plan to follow for future work, building upon technologies developed in the projects [http://www.pathfinder-xquery.org Pathfinder]  and [http://www-db.informatik.uni-tuebingen.de/research/ferry Ferry], both being developed at U Tübingen.
  
 
[1] Garcia M., Prithiviraj R. [http://www.sts.tu-harburg.de/~mi.garcia/pubs/2008/ese/linq4emf.pdf Rethinking the Architecture of O/R Mapping for EMF in terms of LINQ]
 
[1] Garcia M., Prithiviraj R. [http://www.sts.tu-harburg.de/~mi.garcia/pubs/2008/ese/linq4emf.pdf Rethinking the Architecture of O/R Mapping for EMF in terms of LINQ]

Revision as of 14:31, 8 October 2008

Rethinking the Architecture of Java ORM in terms of LINQ

Miguel Garcia (TUHH), Rakesh Prithiviraj (TUHH)

The general theme revolves around the efficient evaluation of LINQ queries in a Java-based implementation. Regarding the outline below, the first two items have already been reported in [1], the remaining are new.


Outline

  1. LINQ set of technologies distilled. Architectural differences between JPA ORM and ADO.NET Entity Framework. Benchmarks for queries on large ORMed Ecore models
  2. LINQ-favored approach to runtime translation into the query language of the target persistent store
  3. Products and prototypes in the Java space aiming at LINQ functionality. We showcase the approach adopted by JaQue, which aims to adopt bytecode inspection to translate LINQ statements into the persistent store's native query language
  4. the venue plan to follow for future work, building upon technologies developed in the projects Pathfinder and Ferry, both being developed at U Tübingen.

[1] Garcia M., Prithiviraj R. Rethinking the Architecture of O/R Mapping for EMF in terms of LINQ

Copyright © Eclipse Foundation, Inc. All Rights Reserved.