ACM Home Page
Please provide us with feedback. Feedback
Safe query objects: statically typed objects as remotely executable queries
Full text PdfPdf (161 KB)
Source International Conference on Software Engineering archive
Proceedings of the 27th international conference on Software engineering table of contents
St. Louis, MO, USA
SESSION: Databases table of contents
Pages: 97 - 106  
Year of Publication: 2005
ISBN:1-59593-963-2
Authors
William R. Cook  University of Texas at Austin
Siddhartha Rai  University of Texas at Austin
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 63,   Citation Count: 18
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1062455.1062488
What is a DOI?

ABSTRACT

Developers of data-intensive applications are increasingly using persistence frameworks such as EJB, Hibernate and JDO to access relational data. These frameworks support both transparent persistence for individual objects and explicit queries to efficiently search large collections of objects. While transparent persistence is statically typed, explicit queries do not support static checking of types or syntax because queries are manipulated as strings and interpreted at runtime. This paper presents Safe Query Objects, a technique for representing queries as statically typed objects while still supporting remote execution by a database server. Safe query objects use object-relational mapping and reflective metaprogramming to translate query classes into traditional database queries. The model supports complex queries with joins, parameters, existentials, and dynamic criteria. A prototype implementation for JDO provides a type-safe interface to the full query functionality in the JDO 1.0 standard.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
S. Alagic and J. Solorzano. Java and OQL: A reflective solution for the impedance mismatch. L'OBJET, 6(2), 2000.
 
2
ANSI/INCITS. Database languages - SQLJ - part 1: SQL routines using the Java programming language. Technical Report 331.1-1999, ANSI/INCITS, 1999.
 
3
4
5
 
6
D. Cengija. Hibernate your data. onJava.com, 2004.
7
8
9
 
10
R. DeLine and M. Fahndrich. Typestates for objects, 2004.
 
11
 
12
G. Hamilton and R. Cattell. JDBC™: A Java SQL API. Sun Microsystems, 1997.
 
13
J. Janke. Compiere project overview. compiere.com, 2004.
 
14
S. P. Jones. Haskell 98 Language and Libraries. Cambridge University Press, 2003.
 
15
16
 
17
V. Matena and M. Hapner. Enterprise Java Beans Specification 1.0. Sun Microsystems, 1998.
 
18
F. Matthes, A. Rudloff, J. Schmidt, and K. Subieta. A gateway from DBPL to Ingres. In W. Litwin and T. Risch, editors, Applications of Databases, First International Conference, ADB-94, volume 819, pages 365--380. Springer-Verlag, 1994.
 
19
E. Meijer and W. Schulte. Programming with rectangles, triangles, and circles. In Proceedings of Conference on XML, 2003.
20
 
21
C. Russell. Java Data Objects (JDO) Specification JSR-12. Sun Microsystems, 2003.
 
22
 
23
D. Tinker. High performance JDO. JDOGenie.com, 2003.
24
 
25
N. Welsh, F. Solsona, and I. Glover. SchemeUnit and SchemeQL: Two little languages. In Third Workshop on Scheme and Functional Programming, 2002.

CITED BY  18

Collaborative Colleagues:
William R. Cook: colleagues
Siddhartha Rai: colleagues