Used - Good 5th Edition May contain highlighting/underlining/notes/etc. May have used stickers on cover. Ships same or next day. Expedited shipping takes 2-3 business days; ...standard shipping takes 4-14 business days.Read moreShow Less
MySQL, Fifth Edition by Paul DuBois The definitive guide to using, programming and administering MySQL 5.5 and MySQL 5.6
MySQL provides a comprehensive guide to effectively using and administering the MySQL database management system (DBMS).
Author Paul DuBois describes everything from the basics of getting information into a database and formulating queries, to using MySQL with PHP or Perl to generate dynamic web pages, to writing your own programs that access MySQL databases, to administering MySQL servers. The book also includes a comprehensive reference section providing detailed information on MySQL’s structure, language, syntax, and APIs.
The fifth edition of this bestselling book has been meticulously revised and updated to thoroughly cover the latest features and capabilities of MySQL 5.5, as well as to add new coverage of features introduced with MySQL 5.6.
MySQL is an open source relational database management system (DBMS) that has experienced a phenomenal growth in popularity and use. Known for its speed and ease of use, MySQL has proven itself to be particularly well-suited for developing database-backed websites and applications. MySQL runs on anything from modest hardware all the way up to enterprise servers, and its performance rivals any database system put up against it.
Paul DuBois' MySQL, Fifth Edition, is the definitive guide to fully exploiting all the power and versatility of MySQL 5.5 and MySQL 5.6
Contents at a Glance
Part I: General MySQL Use
Chapter 1 Getting Started with MySQL
Chapter 2 Using SQL to Manage Data
Chapter 3 Data Types
Chapter 4 Views and Stored Programs
Chapter 5 Query Optimization
Part II: Using MySQL Programming Interfaces
Chapter 6 Introduction to MySQL Programming
Chapter 7 Writing MySQL Programs Using C
Chapter 8 Writing MySQL Programs Using Perl DBI
Chapter 9 Writing MySQL Programs Using PHP
Part III: MySQL Administration
Chapter 10 Introduction to MySQL Administration
Chapter 11 The MySQL Data Directory
Chapter 12 General MySQL Administration
Chapter 13 Security and Access Control
Chapter 14 Database Maintenance, Backups, and Replication
Part IV: Appendixes
Appendix A Software Required to Use This Book
Appendix B Data Type Reference
Appendix C Operator and Function Reference
Appendix D System, Status, and User Variable Reference
Appendix E SQL Syntax Reference
Appendix F MySQL Program Reference
Appendix G C API Reference
Appendix H Perl DBI API Reference
Appendix I PHP API Reference
MySql is a very popular relational database for a number of reasons: it is free for most applications; while not open source it is heavily used by the open source community; and it runs easily on Windows and UNIX. The author's approach is to use two sample databases to explain SQL (structured query) databases with Perl, PHP, and C; administering MySql; and security. This book will be very popular with users who already understand relational databases and are trying to move from Microsoft or Oracle to MySql. Copyright 2000 Cahners Business Information.\
Paul DuBois is a writer, database administrator, and leader in the open source and MySQL communities. He has contributed to the online documentation for MySQL and is the author of MySQL and Perl for the Web (New Riders), MySQL Cookbook, Using csh and tcsh, and Software Portability with imake (O’Reilly). He is currently a technical writer with the MySQL documentation team at Oracle Corporation.
This chapter provides an introduction to the MySQL relational database management system (RDBMS), and to the Structured Query Language (SQL) that MySQL understands. It lays out basic terms and concepts you should understand, describes the sample database we'll be using for examples throughout the book, and provides a tutorial that shows you how to use MySQL to create a database and interact with it.
Begin here if you are new to databases and perhaps uncertain whether or not you need one or can use one.You should also read the chapter if you don't know anything about MySQL or SQL and need an introductory guide to get started. Readers who have experience with MySQL or with database systems might want to skim through the material. However, everybody should read the section "A Sample Database" because it's best if you're familiar with the purpose and contents of the database that we'll be using repeatedly throughout the book.
How MySQL Can Help You
This section describes situations in which the MySQL database system is useful. This will give you an idea of the kinds of things MySQL can do and the ways in which it can help you. If you don't need to be convinced about the usefulness of a database system-perhaps because you've already got a problem in mind and just want to find out how to put MySQL to work helping you solve it-you can proceed to "A Sample Database."
A database system is essentially just a way to manage lists of information. The information can come from a variety of sources. For example, it can represent research data, business records, customer requests, sports statistics, sales reports, personal hobby information, personnel records, bug reports, or student grades. However, although database systems can deal with a wide range of information, you don't use such a system for its own sake. If a job is easy to do already, there's no reason to drag a database into it just to use one. A grocery list is a good example:You write down the items to get, cross them off as you do your shopping, and then throw the list away. It's highly unlikely that you'd use a database for this. Even if you have a palmtop computer, you'd probably use its notepad function for a grocery list, not its database capabilities.
The power of a database system comes in when the information you want to organize and manage becomes voluminous or complex so that your records become more burdensome than you care to deal with by hand. Databases can be used by large corporations processing millions of transactions a day, of course. But even small-scale operations involving a single person maintaining information of personal interest may require a database. It's not difficult to think of situations in which the use of a database can be beneficial because you needn't have huge amounts of information before that information becomes difficult to manage. Consider the following situations:
Your carpentry business has several employees.You need to maintain employee and payroll records so that you know who you've paid and when, and you must summarize those records so that you can report earnings statements to the government for tax purposes. You also need to keep track of the jobs your company has been hired to do and which employees you've scheduled to work on each job.
You run a network of automobile parts warehouses and need to be able to tell which ones have any given part in their inventory so that you can fill customer orders.
As a toy seller, you're particularly subject to fad-dependent demand for items that you carry.You want to know what the current sales trajectory is for certain items so that you can estimate whether to increase inventory (for an item that's becoming more popular) or decrease it (so you're not stuck with a lot of stock for something that's no longer selling well).
That pile of research data you've been collecting over the course of many years needs to be analyzed for publication, lest the dictum "publish or perish" become the epitaph for your career.You want to boil down large amounts of raw data to generate summary information, and to pull out selected subsets of observations for more detailed statistical analysis.
You're a popular speaker who travels the country to many types of assemblies, such as graduations, business meetings, civic organizations, and political conventions.You give so many addresses that it's difficult to remember what you've spoken on at each place you've been, so you'd like to maintain records of your past talks and use them to help you plan future engagements. If you return to a place at which you've spoken before, you don't want to give a talk similar to one you've already delivered there, and a record of each place you've been would help you avoid repeats.You'd also like to note how wen your talks are received. (Your address "Why I Love Cats" to the Metropolitan Kennel Club was something of a dud, and you don't want to make that mistake again the next time you're there.)
You're a teacher who needs to keep track of grades and attendance. Each time you give a quiz or a test, you record every student's grade. It's easy enough to write down scores in a gradebook, but using the scores later is a tedious chore. You'd rather avoid sorting the scores for each test to determine the grading curve, and you'd really rather not add up each student's scores when you determine final grades at the end of the grading period. Counting each student's absences is no fun, either.
The organization for which you are the secretary maintains a directory of members. (The organization could be anything-a professional society, a club, a repertory company, a symphony orchestra, or an athletic booster club.) You generate the directory in printed form each year for members, based on a word processor document that you edit as membership information changes.
You're tired of maintaining the directory that way because it limits what you can do with it. It's difficult to sort the entries in different ways, and you can't easily select just certain parts of each entry (such as a list consisting only of names and phone numbers). Nor can you easily find a subset of members, such as those who need to renew their memberships soon-if you could, it would eliminate the job of looking through the entries each month to find those members who need to be sent renewal notices.
Also, you'd really like to avoid doing all the directory editing yourself, but the society doesn't have much of a budget, and hiring someone is out of the question.You've heard about the "paperless office" that's supposed to result from electronic record-keeping, but you haven't seen any benefit from it. The membership records are electronic, but, ironically, aren't in a form that can be used easily for anything except generating paper by printing the directory!
These scenarios range from situations involving large amounts to relatively small amounts of information. They share the common characteristic of involving tasks that can be performed manually but that could be performed more efficiently by a database system.
What specific benefits should you expect to see from using a database system such as MySQL? It depends on your particular needs and requirements-and as seen in the...
MySQL by Paul Dubois recently was reissued in a fifth edition. I
MySQL by Paul Dubois recently was reissued in a fifth edition. I purchased my first edition of this book more than a dozen years ago and it has become heavily dog-eared, festooned with Post-Its, and hand annotated over the years. It has proven to be the ‘go-to’ book when other books or the manuals did not explain to my satisfaction any questions that have popped up. The author is part of the amazing MySQL Documentation Team for Oracle and certainly knows the subject. At 1,154 pages it is not light in weight nor light in detail. The chapters include ‘Data Types’, ‘Writing MySQL Programs using C’, ‘Security and Access Control’, ‘System, Status and User Variable Reference’, ‘Query Optimization’, ‘Writing MySQL Programs using PHP’, and ‘The MySQl Data Dictionary’. The layout is easy on the eyes and the examples are able to spotlight the idea being covered fully. The text itself reads easily and amazingly clear. This is the most complete single book on MySQL and the one book you would bring if you have to use MySQL on the fabled desert island that allows only one book. The book is detailed enough for gnarled DBAs to discover undiscovered gems while clear enough for a junior MySQL-er to be able to get through a rough spot.
if you run across this book in a store, head directly to chapter 13 on Security and Access Control where ‘How to Steal Data’ provides any DBA a Steven King level horror story that will provide nightmare fodder for years to come. The author then guides you through MySQL security and provides the best details on Proxy Accounts I have found. Other chapters are equally profound and perfectly detailed.
It does cover some of the new features of MySQL 5.6 but 5.6 came out after this book was committed to publishing. This is a minor problem and should not stop anyone from getting a copy of this book in their hands ASAP.
And I apologize to Paul and his publisher for what I will do to this book in the next few years as I make notes, add Post-Its, fold corners on certain pages. This is a physically beautiful book that will look like a sea anemone as I make good use of it.
Was this review helpful? YesNoThank you for your feedback.Report this reviewThank you, this review has been flagged.