Getting Startedwith pureQuery

More documents

Recommendations

Info

170 Getting Started with pureQuery Figure 9.1 - The pureQuery platform enhances data access for a variety of persistence frameworks. Object-relational mapping refers to the process of transferring data back and forth (mapping) between the object-oriented software layer and an underlying relational database. Object-relational mapping is one of the services provided by persistence frameworks that use a relational database backend. The goal of the object-relational mapping layer is to transfer data efficiently and correctly between two different paradigms – object and relational – such that neither the performance nor data integrity of either is lost. The object-relational mapping layer encapsulates knowledge of the relational database layer, so business logic can be designed independently from the database schema. The software engineering benefits of encapsulation include the ability for each layer to be optimized individually, and the reduction of the impact of maintenance, upgrades, or redesign of either layer to the other. pureQuery’s object-relational mapping tools automate the development of an optimized object-relational mapping layer, and minimize the time, effort, and system resources required to develop, maintain, manage, and run the data access application. 9.1.1 pureQuery and Persistence Frameworks pureQuery integrates with a variety of persistence frameworks to provide improved development time, manageability, security, and performance for framework applications.
9.1.1.1 JPA Chapter 9 – Persistence Frameworks and Data Access: Context for pureQuery 171 The Java Persistence API (JPA) has become the current de-facto standard for Java persistence. JPA delivers persistence support for both JSE and JEE applications. Implementations of JPA are available in the open source community and from a variety of vendors, including IBM’s Websphere Application Server. See Chapter 16 for more information about features designed to make development, management, and monitoring of JPA applications quicker with pureQuery. 9.1.1.2 Hibernate and iBatis Hibernate and iBatis are open-source projects that provide object-relational mapping tools, API’s, and object-relational persistence. They continue to release new versions to provide such features as stronger and simpler object relational mapping supporting complex joins, queries from multiple tables, and automated mapping for object heirarchies and n- cardinality relationships. pureQuery integration with Hibernate and iBatis accelerates data access from either of these frameworks. Accelaration of Hibernate and iBatis applications can be achieved using the pureQuery Client Optimizer, described in Chapter 6. 9.2 pureQuery APIs in Context There is no “one size fits all” solution for a data access layer. The ideal mapping solution varies depending on the type of data store, the database schema if it’s a database, and what types of business objects and processes are represented in the object layer. As a result, pureQuery tooling supports a variety of access layer paradigms, from quick, generated, simple table-to-class maps, to tools that support advanced fine-tuning for complex query results. pureQuery makes it easy to implement the core J2EE patterns Data Access Object, which abstracts and encapsulates persistent data access, and Transfer Object, which encapsulates the business data, in a variety of ways. For example, pureQuery can quickly create the simplest type of object-relational map, which defines one class for each relational table. The class contains a field for each column in a table, and each instance represents a row in the table, following the active record and rowset patterns. However, a more complex mapping solution is required under many common data access circumstances and pureQuery provides intuitive support for these as well. If the same data is stored in several classes/tables (as often happens since classes represent interconnected real-world objects), a simple class-to-table map breaks during normalization. This is because normalization ensures the data is represented in only one table in the database. Object-relational mapping must therefore be fine-tuned after database normalization. pureQuery provides a comprehensive and flexible set of approaches for creating a data access layer. It supports integration of relational data, object, and xml data. It supports a variety of data servers and supports mixed queries across data servers and in-memory cache objects using standard SQL.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7:
Trademarks IBM, the IBM logo, DB2,
Page 10 and 11:
10 Getting Started with pureQuery 3
Page 12 and 13:
12 Getting Started with pureQuery C
Page 14 and 15:
Page 16 and 17:
16 Getting Started with pureQuery C
Page 18 and 19:
18 Getting Started with pureQuery m
Page 20 and 21:
20 Getting Started with pureQuery T
Page 22 and 23:
22 Getting Started with pureQuery K
Page 24 and 25:
24 Getting Started with pureQuery A
Page 27 and 28:
1 Chapter 1 - Introduction to pureQ
Page 29 and 30:
Chapter 1 - Introduction to pureQue
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
2 Chapter 2 - Installing pureQuery
Page 47 and 48:
Chapter 2 - Installing pureQuery (O
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61:
PART II - TOOLING
Page 66 and 67:
66 Getting Started with pureQuery F
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
72 Getting Started with pureQuery t
Page 74 and 75:
74 Getting Started with pureQuery A
Page 76 and 77:
76 Getting Started with pureQuery T
Page 78 and 79:
78 Getting Started with pureQuery a
Page 80 and 81:
80 Getting Started with pureQuery r
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
86 Getting Started with pureQuery Y
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
92 Getting Started with pureQuery D
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
98 Getting Started with pureQuery
Page 100 and 101:
Page 102 and 103:
Page 105 and 106:
PART III - SECURITY, PERFORMANCE, A
Page 107 and 108:
6 Chapter 6 - The Client Optimizer:
Page 109 and 110:
Chapter 6 - The Client Optimizer: p
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120: Chapter 6 - The Client Optimizer: p
Page 137 and 138: 7 Chapter 7 - The StaticBinder Util
Page 139 and 140: Chapter 8 - Extended Insight 139 No
Page 141 and 142: 7.2.2.3 Changes to pureQueryXml fil
Page 143 and 144: Chapter 8 - Extended Insight 143 Fi
Page 145 and 146: Chapter 8 - Extended Insight 145 Fi
Page 147 and 148: Chapter 8 - Extended Insight 147 -u
Page 149 and 150: Chapter 8 - Extended Insight 149 7.
Page 151 and 152: Chapter 8 - Extended Insight 151 ne
Page 153: Chapter 8 - Extended Insight 153 11
Page 156 and 157: 156 Getting Started with pureQuery
Page 169: 9 Chapter 9 - Persistence Framework
Page 173 and 174: Chapter 9 - Persistence Frameworks
Page 181: Chapter 9 - Persistence Frameworks
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 243 and 244:
12 Chapter 12 - Stored Procedures T
Page 245 and 246:
Chapter 12 - Stored Procedures 245
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
13 Chapter 13 - Handlers In this ch
Page 263 and 264:
Chapter 13 - Handlers 263 Figure 13
Page 265 and 266:
Chapter 13 - Handlers 265 SELECT *
Page 267 and 268:
Chapter 13 - Handlers 267 construct
Page 269 and 270:
13.4.1 Writing a ResultHandler impl
Page 271 and 272:
Chapter 13 - Handlers 271 functiona
Page 273 and 274:
Chapter 13 - Handlers 273 Listing 1
Page 275 and 276:
Chapter 13 - Handlers 275 package h
Page 277:
A. In a getData method in the com.i
Page 281 and 282:
14 Chapter 14 - Best Practices In t
Page 283 and 284:
Chapter 14 - Best Practices 283 @Se
Page 285 and 286:
Chapter 14 - Best Practices 285 Fig
Page 287 and 288:
15 Chapter 15 - pureQuery and pureX
Page 289 and 290:
Chapter 15 - pureQuery and pureXML
Page 291 and 292:
Page 293:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 305 and 306:
A Appendix A - Solutions to the rev
Page 307 and 308:
Appendix A - Solutions to the revie
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
B Appendix B - Understanding the Sa
Page 315 and 316:
B.1.3 The “Employee Information
Page 317 and 318:
Appendix C - Up and Running with DB
Page 319 and 320:
B.1.6 The “Company Employees” s
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
C.4.1 IBM Optim Development Studio
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 355 and 356:
E Appendix E - Options Files This a
Page 357 and 358:
Appendix E - Options files 357 comm
Page 359:
Appendix E - Options files 359 In b
Page 363 and 364:
Resources Web sites 1. pureQuery pl
show all

Getting Startedwith pureQuery

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?