MySQL Internals Manual :: 24 Writing a Custom Storage Engine
Section Navigation [Toggle]
- Preface and Legal Notice
- 1 A Guided Tour Of The MySQL Source Code
- 2 Coding Guidelines
- 3 Reusable Classes and Templates
- 4 How to Build MySQL Server with CMake
- 5 Autotools to CMake Transition Guide
- 6 Plugins
- 7 Transaction Handling in the Server
- 8 The Optimizer
- 9 Tracing the Optimizer
- 10 Memory Allocation
- 11 Important Algorithms and Structures
- 12 File Formats
- 13 How MySQL Performs Different Selects
- 14 How MySQL Transforms Subqueries
- 15 MySQL Client/Server Protocol
- 16 Stored Programs
- 17 Prepared Statement and Stored Routine Re-Execution
- 18 Writing a Procedure
- 19 Replication
- 20 The Binary Log
- 21 MySQL Backup
- 22 MyISAM Storage Engine
- 23 InnoDB Storage Engine
- 24 Writing a Custom Storage Engine
- 24.1 Additional Resources
- 24.2 Overview
- 24.3 Creating Storage Engine Source Files
- 24.4 Adding Engine Specific Variables and Parameters
- 24.5 Creating the handlerton
- 24.6 Handling Handler Instantiation
- 24.7 Defining Filename Extensions
- 24.8 Creating Tables
- 24.9 Opening a Table
- 24.10 Implementing Basic Table Scanning
- 24.11 Closing a Table
- 24.12 Adding Support for INSERT to a Storage Engine
- 24.13 Adding Support for UPDATE to a Storage Engine
- 24.14 Adding Support for DELETE to a Storage Engine
- 24.15 Supporting Non-Sequential Reads
- 24.16 Supporting Indexing
- 24.17 Supporting Transactions
- 24.18 API Reference
- 24.19 FAQ
- 25 Test Synchronization
- 26 Injecting Test Faults
- 27 How to Create Good Test Cases
- 28 Porting to Other Systems
- 29 Error Messages
- A MySQL Source Code Distribution
- B InnoDB Source Code Distribution
- Index
Table of Contents [+/-]
- 24.10.1. Implementing the
store_lock()Method - 24.10.2. Implementing the
external_lock()Method - 24.10.3. Implementing the
rnd_init()Method - 24.10.4. Implementing the
info(uinf flag)Method - 24.10.5. Implementing the
extra()Method - 24.10.6. Implementing the
rnd_next()Method
INSERT to a Storage EngineUPDATE to a Storage EngineDELETE to a Storage Engine- 24.16.1. Indexing Overview
- 24.16.2. Getting Index Information During
CREATE TABLEOperations - 24.16.3. Creating Index Keys
- 24.16.4. Parsing Key Information
- 24.16.5. Providing Index Information to the Optimizer
- 24.16.6. Preparing for Index Use with
index_init() - 24.16.7. Cleaning up with
index_end() - 24.16.8. Implementing the
index_read()Method - 24.16.9. Implementing the
index_read_idx()Method - 24.16.10. Implementing the
index_read_last()Method - 24.16.11. Implementing the
index_next()Method - 24.16.12. Implementing the
index_prev()Method - 24.16.13. Implementing the
index_first()Method - 24.16.14. Implementing the
index_last()Method
- 24.18.1. bas_ext
- 24.18.2. close
- 24.18.3. create
- 24.18.4. delete_row
- 24.18.5. delete_table
- 24.18.6. external_lock
- 24.18.7. extra
- 24.18.8. index_end
- 24.18.9. index_first
- 24.18.10. index_init
- 24.18.11. index_last
- 24.18.12. index_next
- 24.18.13. index_prev
- 24.18.14. index_read
- 24.18.15. index_read_idx
- 24.18.16. index_read_last
- 24.18.17. info
- 24.18.18. open
- 24.18.19. position
- 24.18.20. records_in_range
- 24.18.21. rnd_init
- 24.18.22. rnd_next
- 24.18.23. rnd_pos
- 24.18.24. start_stmt
- 24.18.25. store_lock
- 24.18.26. update_row
- 24.18.27. write_row
With MySQL 5.1, MySQL AB has introduced a pluggable storage engine architecture that makes it possible to create new storage engines and add them to a running MySQL server without recompiling the server itself.
This architecture makes it easier to develop new storage engines for MySQL and deploy them.
This chapter is intended as a guide to assist you in developing a storage engine for the new pluggable storage engine architecture.
Copyright © 1997, 2012, Oracle and/or its affiliates. All
rights reserved.
Legal Notices
