Michelle Malcher - Oracle Database 11g & MySQL 5.6 Developer Handbook

About the Author

Michael McLaughlin is a professor of Computer Information Technology at Brigham Young UniversityIdaho. He is also an Oracle ACE. Michael has worked with the Oracle product stack for 20 years as a developer, DBA, and E-Business Suite Applications DBA.

Michael left Oracle as the Senior Upgrade Manager in Release Engineering for the Oracle Applications Division. He worked at Oracle for more than eight years in consulting, support, and development. He is the inventor of the ATOMS transaction architecture (U.S. Patents #7,206,805 and #7,290,056). The patents are assigned to Oracle Corporation.

He is the author of six books on Oracle technology, including Oracle Database 11g PL/SQL Programming and Oracle Database 10g PL/SQL Programming.

Michael and his wife, Lisa, have been married for more than 20 years and they have nine children. They live in Idaho near Yellowstone National Park.

About the Technical Editor

A. Scott Mikolaitis is an applications architect at Oracle Corporation and has worked at Oracle for more than ten years. He works on prototyping and standards development for the SOA technology in Oracle Fusion.

Scott also enjoys working with web services in Java as well as Jabber for human and system interaction patterns. He spends his spare time on DIY home improvement and gas-fueled RC cars.

Michael McLaughlin

New York Chicago San Francisco
Lisbon London Madrid Mexico City Milan
New Delhi San Juan Seoul Singapore Sydney Toronto

Copyright 2012 by The McGraw-Hill Companies, Inc. (Publisher). All rights reserved. Except as permitted under the United States Copyright Act of 1976, no part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of the publisher.

ISBN 978-0-07-176886-3
MHID 0-07-176886-6

The material in this eBook also appears in the print version of this title: ISBN 978-0-07-176885-6, MHID 0-07-176885-8.

All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trademarked name, we use names in an editorial fashion only, and to the benefit of the trademark owner, with no intention of infringement of the trademark. Where such designations appear in this book, they have been printed with initial caps.

McGraw-Hill eBooks are available at special quantity discounts to use as premiums and sales promotions, or for use in corporate training programs. To contact a representative please e-mail us at bulksales@mcgraw-hill.com.

TERMS OF USE

This is a copyrighted work and The McGraw-Hill Companies, Inc. (McGraw-Hill) and its licensors reserve all rights in and to the work. Use of this work is subject to these terms. Except as permitted under the Copyright Act of 1976 and the right to store and retrieve one copy of the work, you may not decompile, disassemble, reverse engineer, reproduce, modify, create derivative works based upon, transmit, distribute, disseminate, sell, publish or sublicense the work or any part of it without McGraw-Hills prior consent. You may use the work for your own noncommercial and personal use; any other use of the work is strictly prohibited. Your right to use the work may be terminated if you fail to comply with these terms.

THE WORK IS PROVIDED AS IS. McGRAW-HILL AND ITS LICENSORS MAKE NO GUARANTEES OR WARRANTIES AS TO THE ACCURACY, ADEQUACY OR COMPLETENESS OF OR RESULTS TO BE OBTAINED FROM USING THE WORK, INCLUDING ANY INFORMATION THAT CAN BE ACCESSED THROUGH THE WORK VIA HYPERLINK OR OTHERWISE, AND EXPRESSLY DISCLAIM ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. McGraw-Hill and its licensors do not warrant or guarantee that the functions contained in the work will meet your requirements or that its operation will be uninterrupted or error free. Neither McGraw-Hill nor its licensors shall be liable to you or anyone else for any inaccuracy, error or omission, regardless of cause, in the work or for any damages resulting therefrom. McGraw-Hill has no responsibility for the content of any information accessed through the work. Under no circumstances shall McGraw-Hill and/or its licensors be liable for any indirect, incidental, special, punitive, consequential or similar damages that result from the use of or inability to use the work, even if any of them has been advised of the possibility of such damages. This limitation of liability shall apply to any claim or cause whatsoever whether such claim or cause arises in contract, tort or otherwise.

To Lisa, my eternal companion, inspiration, wife,
and best friend; and to Sarah, Joseph, Elise, Ian,
Ariel, Callie, Nathan, Spencer, and Christianne,
who supported me like the champions they are
throughout the writing process.

PART I
Development Components

PART II
SQL Development

PART I
Development Components

PART II
SQL Development

Many thanks go to Wendy Rinaldi and Stephanie Evans at McGraw-Hill for their tireless work on this project, and their support throughout the project.

Special thanks go to Ian McLaughlin, who proofread for me. Thanks to Kent Jackson for looking over outlines; Michael Stokes, Benjamin Benson, and William Graham for editing and testing code components; Rex Barzee for letting me brainstorm organizational ideas; and Art Ericson, my CIT Department Chair, for his support on the project.

Finally, no acknowledgment would be complete without thanking the production department for their conscientious attention to detail and hard work in putting all the pieces together. Id like to thank Lisa Theobold for smoothing my writing, Bev Weiler for finding errors of omission and commission and tuning the organization of content, and Sandhya Gola for keeping things organized through copy edit, proof edit, and final book preparation.

The Introduction is always the last thing you write, and Ive sometimes thought it should be the first thing you write. This time I drafted the introduction before writing and it helped me make sure I stayed a planned course. The production staff also helps clear up what I write, and you can check my acknowledgment page recognizing them and their talents, which are critical to bring a quality book into print.