Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering phpMyAdmin 3.4 for Effective MySQL Management

You're reading from   Mastering phpMyAdmin 3.4 for Effective MySQL Management A complete guide to getting started with phpMyAdmin 3.4 and mastering its features book and ebook

Arrow left icon
Product type Paperback
Published in Feb 2012
Publisher Packt
ISBN-13 9781849517782
Length 394 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (27) Chapters Close

Mastering phpMyAdmin 3.4 for Effective MySQL Management
Credits
About the Author
About the Reviewers
www.PacktPub.com
1. Preface
1. Getting Started with phpMyAdmin FREE CHAPTER 2. Configuring Authentication and Security 3. Over Viewing the Interface 4. Creating and Browsing Tables 5. Changing Data and Structure 6. Exporting Structure and Data (Backup) 7. Importing Structure and Data 8. Searching Data 9. Performing Table and Database Operations 10. Benefiting from the Relational System 11. Entering SQL Statements 12. Generating Multi-table Queries 13. Synchronizing Data and Supporting Replication 14. Using Query Bookmarks 15. Documenting the System 16. Transforming Data using MIME 17. Supporting Features Added in MySQL 5 18. Tracking Changes 19. Administrating the MySQL Server Troubleshooting and Support Index

Principles


This section defines important principles on which the tracking mechanism is based: versioning, snapshot, and the archiving issues of tracking information.

Versioning

Using version numbers is something we are familiar with; for example, this book describes phpMyAdmin version 3.4.x. However, at this point we must understand exactly why we use version numbers.

A good reference on software versioning is located in Wikipedia at http://en.wikipedia.org/wiki/Software_versioning. This article mentions that version names can be used, but version numbers are more common. More importantly, it states that version numbers "correspond to new developments in the software".

If we apply this principle to database development, the decision that a table is ripe for a new version should be made by the development team when a significant change is about to occur on this table. How significant the change has to be in order to trigger a new version is a matter of interpretation within the team. At least...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image