MindMap Gallery How MySQL works
Study notes on the working principle of MySQL, a picture to help you understand the technical details of MySQL. The content is practical, if you need it, collect it quickly!
Edited at 2024-04-08 14:14:05This is a flowchart illustrating the process of archiving monthly failure analysis reports and tracking the implementation of improvement measures. The diagram is structured into five main steps, each with specific tasks and sub-tasks.Monthly Report Collection & Organization: This step involves collecting failure analysis reports from various departments, reviewing them for completeness, and categorizing them by product, failure mode, and severity. Root Cause Analysis & Statistics: Here, the focus is on categorizing causes, analyzing trends, identifying root causes, and compiling statistics on high-frequency failure modes and key components. Improvement Measure Formulation & Assignment: This step includes formulating improvement measures, assigning responsibilities, and setting timelines for implementation.Measure Implementation Tracking & Verification: It involves tracking the progress of implementation, verifying effectiveness, and confirming issue closure.Knowledge Base Update & Monthly Report Output: The final step covers archiving reports, updating the knowledge base, and compiling monthly summaries.This template can be easily reused and adapted using tools like EdrawMind to suit different organizational needs.
This is a timeline infographic detailing the annual product certification acquisition countdown process, structured into four sequential phases. The first phase, Certification Planning & Initiation, encompasses goal setting, timeline planning, resource preparation, defining specific certification objectives such as CCC/CE/FCC, formulating an annual plan with key milestones, and allocating necessary budget, personnel, and sample resources. Following this, the Application & Testing Phase involves material submission, coordination with certification agencies, core testing procedures, preparation of technical documents, application forms, and samples, selection of the appropriate certification agency, and execution of critical safety, EMC, and RF tests. The subsequent Rectification & Acquisition Phase focuses on addressing and rectifying any identified issues, re-verification processes, acquisition of the certificate, analysis of test issues, implementation of necessary fixes, and modification of samples for supplemental testing. Finally, the Countdown Monitoring phase emphasizes tracking progress, managing risks, monitoring remaining days and key milestones, managing time, technical, and cost risks, and maintaining effective internal and external communication throughout the process. This comprehensive template can be readily reused and adapted using tools like EdrawMind to meet diverse organizational requirements.
This is a flowchart detailing the weekly update and review plan for technical documents. The process is divided into six main stages, each with specific tasks and responsibilities. It begins with Weekly Planning, where the document scope is defined, update objectives are set, and schedules are arranged. Next, Document Updates involve maintaining various documents such as hardware design documents, test specifications, and BOM tables, alongside version control and archiving. Internal Review Preparation follows, focusing on compiling review materials, identifying participants, and setting agendas. The Review Meeting stage includes document examination, problem discussion, decision recording, and responsibility allocation. After the meeting, Review Feedback Processing takes place, involving issue tracking, document modification, quality checks, and closure verification. Finally, Output Deliverables are prepared, including official release versions, release notifications, review reports, and plans for the next week. This structured approach ensures systematic and efficient management of technical documents, and the template can be easily adapted using tools like EdrawMind.
This is a flowchart illustrating the process of archiving monthly failure analysis reports and tracking the implementation of improvement measures. The diagram is structured into five main steps, each with specific tasks and sub-tasks.Monthly Report Collection & Organization: This step involves collecting failure analysis reports from various departments, reviewing them for completeness, and categorizing them by product, failure mode, and severity. Root Cause Analysis & Statistics: Here, the focus is on categorizing causes, analyzing trends, identifying root causes, and compiling statistics on high-frequency failure modes and key components. Improvement Measure Formulation & Assignment: This step includes formulating improvement measures, assigning responsibilities, and setting timelines for implementation.Measure Implementation Tracking & Verification: It involves tracking the progress of implementation, verifying effectiveness, and confirming issue closure.Knowledge Base Update & Monthly Report Output: The final step covers archiving reports, updating the knowledge base, and compiling monthly summaries.This template can be easily reused and adapted using tools like EdrawMind to suit different organizational needs.
This is a timeline infographic detailing the annual product certification acquisition countdown process, structured into four sequential phases. The first phase, Certification Planning & Initiation, encompasses goal setting, timeline planning, resource preparation, defining specific certification objectives such as CCC/CE/FCC, formulating an annual plan with key milestones, and allocating necessary budget, personnel, and sample resources. Following this, the Application & Testing Phase involves material submission, coordination with certification agencies, core testing procedures, preparation of technical documents, application forms, and samples, selection of the appropriate certification agency, and execution of critical safety, EMC, and RF tests. The subsequent Rectification & Acquisition Phase focuses on addressing and rectifying any identified issues, re-verification processes, acquisition of the certificate, analysis of test issues, implementation of necessary fixes, and modification of samples for supplemental testing. Finally, the Countdown Monitoring phase emphasizes tracking progress, managing risks, monitoring remaining days and key milestones, managing time, technical, and cost risks, and maintaining effective internal and external communication throughout the process. This comprehensive template can be readily reused and adapted using tools like EdrawMind to meet diverse organizational requirements.
This is a flowchart detailing the weekly update and review plan for technical documents. The process is divided into six main stages, each with specific tasks and responsibilities. It begins with Weekly Planning, where the document scope is defined, update objectives are set, and schedules are arranged. Next, Document Updates involve maintaining various documents such as hardware design documents, test specifications, and BOM tables, alongside version control and archiving. Internal Review Preparation follows, focusing on compiling review materials, identifying participants, and setting agendas. The Review Meeting stage includes document examination, problem discussion, decision recording, and responsibility allocation. After the meeting, Review Feedback Processing takes place, involving issue tracking, document modification, quality checks, and closure verification. Finally, Output Deliverables are prepared, including official release versions, release notifications, review reports, and plans for the next week. This structured approach ensures systematic and efficient management of technical documents, and the template can be easily adapted using tools like EdrawMind.
MySQL
Database definition
database
A physically manipulated file system or other collection of file types
Example
Composed of background threads and a shared memory area
Contains two processes mysqld and mysqld_safe
relation
one-to-one correspondence
Manipulate database files through database instances
An instance is a dedicated interface provided by the database to the upper layer for operations.
Architecture
connection handling
Query parsing, caching, optimization
storage engine
InnoDB
MyISAM
Storage (InnoDB)
logical space
tablespace
segment
area
The extent size and number of pages it contains will vary depending on the page size
Minimum 1MB
Contain at least 64 pages
page
Default 16KB
innodb_page_size
table storage
.frm
Storage table definition
.ibd
Store data index
record storage
Compact
Arrange the length of variable-length fields in reverse order at the beginning of the line
Redundant
Record the offset of each column at the beginning of the row
Antelope
When storing large objects, the data page records 768 bytes, and the subsequent offset points to the overflow page.
Compressed
Dynamic
Barracuda
Recording large objects only retains 20-byte pointers, and the actual data is in the overflow page
data page
Minimum disk unit
The nodes in B-Tree record page information
structure
File Header/Fil Trailer
Record header information
Page Header/Page Directory
Record page status information
Infimum/Supremum
The minimum and maximum values of the primary key of this page
User Records
actual storage records
Stored in linked list structure
Free Space
free space