Getting Startedwith pureQuery

More documents

Recommendations

Info

28 Getting Started with pureQuery 1.1.1 What’s in a name? pureQuery is the name IBM has chosen to represent a data access platform that can help optimize and secure data access. It was first released publicly in October 2007 as part of what was then known as the “Data Studio” family (now known as the “Optim” product family). (More on the history of pureQuery can be found on Wikipedia [1]). Because you may be familiar with the term pureXML® from what you’ve read in Getting Started with DB2 Express-C, it’s interesting to get a little background on how this data access platform ended up with the name pureQuery. Stephen Brodsky, an IBM Distinguished Engineer in the IBM Optim organization, in one of his blog entries, says it best: So how did this platform get the name pureQuery? It didn’t start out that way (as is often the case with new products or technologies). We had two internal code names for the project, Data Zero (because it’s the data access layer for Project Zero) and JLinQ, because it compares very favorably with Microsoft®'s LINQ initiative (all the power of database access without having to change the C# and Visual Basic languages – we achieved all the major features of LINQ but stayed pure standard Java). pureQuery embraces the full database access without watering down the SQL or database capabilities. It avoids least common denominator approaches that dilute the ability to access what you really need in a database and integrates all aspects of the life cycle in both runtime and tooling, "Pure" means no compromises and first class Java-SQL-database integration. As the project moved closer to release, it was time to choose a name. Because the project represented application plus database integration at what we feel is the best, truest form, without all the mess that sometimes bogs software down, early users called it "pure data access" or "pure data query (PDQ)." The pure concept, and the PDQ acronym, really resonated with the marketing team (the same team that named pureXML), and the pureQuery name was born. [2] It’s important to note here that since Steve wrote that blog entry, a subset of pureQuery benefits have been extended beyond Java data access, including to .NET, and by the time this book is published, CLI. The focus of this Getting Started book is on the support for Java environments.
Chapter 1 – Introduction to pureQuery 29 1.1.2 What do we mean by platform? IBM calls pureQuery a “platform” because it seems to be the best word to express the vision of pureQuery as a technology that spans the data management lifecycle. In other words, there are aspects of pureQuery that are embedded in design, development, test, deployment, monitoring, and optimization. (For more information about how IBM defines the data management lifecycle, see the e-book Getting Started with Data Studio for DB2.) pureQuery consists of the facets shown in Figure 1.1, which can be used as needed for any particular project or task and which are delivered in specific products related to those tasks. Figure 1.1 - Facets of pureQuery data access platform • Application programming interfaces (APIs), built for ease of use and for simplifying the use of best practices for enhanced database performance when using Java. • A runtime, which provides optimized and secure database access • An Eclipse-based integrated database development environment (IDE) for enhancing development productivity, improving data access performance during development, and improving collaboration between developers and DBAs • Monitoring services, to provide developers and DBAs with previously unknown insights about performance of Java and CLI database applications.
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: 14 Getting Started with pureQuery 1
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: 1 Chapter 1 - Introduction to pureQ
Page 31 and 32: Chapter 1 - Introduction to pureQue
Page 45 and 46: 2 Chapter 2 - Installing pureQuery
Page 47 and 48: Chapter 2 - Installing pureQuery (O
Page 61: PART II - TOOLING
Page 66 and 67: 66 Getting Started with pureQuery F
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:
82 Getting Started with pureQuery F
Page 84 and 85:
84 Getting Started with pureQuery 4
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:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
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:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 169 and 170:
9 Chapter 9 - Persistence Framework
Page 171 and 172:
9.1.1.1 JPA Chapter 9 - Persistence
Page 173 and 174:
Chapter 9 - Persistence Frameworks
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
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

Create successful ePaper yourself

Delete template?

Save as template?