Introduction
- I don't care.
- MySQL is a relational database management system (RDBMS). It is an open-source, multi-user, multi-threaded database system that allows for storing and managing structured data in tables. It uses the Structured Query Language (SQL) to manage and manipulate data.
Key Features of MySQL:
- Open Source
- Cross-Platform
- Relational Database: MySQL is based on a relational database model, which stores data in tables (also known as relations).
- High Performance: It is optimized for speed and can handle a large amount of data efficiently.
-
ACID Compliant: MySQL supports the ACID (Atomicity, Consistency, Isolation, Durability) properties, ensuring that database transactions are processed reliably.
- Atomicity ensures that a transaction is treated as a single, indivisible unit. Either all of the operations within a transaction are completed successfully, or none of them are applied. In other words, a transaction is atomic: it is "all or nothing."
- Consistency ensures that a transaction takes the database from one valid state to another valid state. After a transaction, all data must be in a consistent state, adhering to all defined rules, constraints, and relationships.
- Isolation ensures that transactions are executed in isolation from one another, even if they occur concurrently. Each transaction should be executed as if it is the only transaction being processed, preventing interference from other transactions.
- Durability ensures that once a transaction is committed, it is permanent, even in the case of system failures like power outages or crashes. The changes made by the transaction are saved to disk and will survive any subsequent failures.
- Multi-User Access: MySQL allows multiple users to access the database simultaneously without affecting performance.
SQL Keywords
CREATE
-
CREATE DATABASE
- The CREATE DATABASE command is used to create a new database. In Mongoose, you don't need to explicitly create a database; it is automatically created when you connect to the database.
// DB is created if it doesn't exist mongoose.connect('mongodb://localhost/my_database');
CREATE DATABASE my_database;
-
USE DATABASE
- The USE DB_NAME is used to select the database to use. In Mongoose, this is handled by the connection string.
mongoose.connect('mongodb://localhost/my_database');
USE my_database;
-
CREATE TABLE
- The CREATE TABLE command is used to create a new table in the database. In Mongoose, this is similar to creating a new collection.
// DB is created if it doesn't exist mongoose.connect('mongodb://localhost/my_database');
CREATE DATABASE my_database;
-
CREATE INDEX
- The CREATE INDEX command is used to create an index on a table to improve query performance. In MongoDB, this is the same.
mongoose.connect('mongodb://localhost/my_database');
USE my_database;
DESCRIBE
- Used in SQL to view the structure of a table (its columns, data types, constraints, etc.). Mongoose Example: In MongoDB, there isn't a direct equivalent to DESCRIBE. However, you can inspect a schema programmatically.
mongoose.model('User', UserSchema);
CREATE TABLE Users ( id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100) NOT NULL, email VARCHAR(100) NOT NULL UNIQUE );
INSERT
- The INSERT INTO command is used to insert new rows in a table. In mongoose you would insert a new document into a collection/(Model).
UserSchema.index({ email: 1 }); // Unnamed Index UserSchema.index({ email: 1 }, { name: 'idx_email' }); // Named Index
-- Syntax: CREATE INDEX index_name ON table_name (column_name); CREATE INDEX idx_email ON Users (email); -- Named Index CREATE INDEX ON Users (email); -- Unnamed Index
SELECT
- The SELECT statement in SQL is used to retrieve data from a database. In Mongoose, this is equivalent to using the .find() method to query a collection.
console.log(UserSchema.paths); // Outputs details about the schema fields and types
DESCRIBE Users;
UPDATE
- The UPDATE statement is used to modify the existing records in a table. In mongoose you use find and update or .update()
// In mongoose its equivalent to .save() or .create(); const newUser = new User({ name: 'John Doe', email: 'john@example.com' }); newUser.save()
INSERT INTO Users (name, email) VALUES ('John Doe', 'john@example.com');
DELETE
- The DELETE statement is used to delete existing records in a table. In mongoose we'd use deleteOne, deleteMany or find and delete.
const users = await User.find(); // Fetches all users const { name, email } = await User.findById(1); // Fetches user with id = 1
SELECT * FROM Users; -- all users SELECT name, email FROM Users WHERE id = 1; -- user of id 1
ALTER
- The ALTER TABLE statement in SQL is used to modify the structure of an existing table (add column, drop column and modify column). In Mongoose, the equivalent operation would be modifying the schema to include the new field and then handling updates to existing documents if necessary.
// update all user of name kb const query = { name: "kb" }; User.update(query, { name: "thekbbohara" })
-- update all user of name kb UPDATE Users SET name = "thekbbohara", email = "thekbbohara@gmail.com" WHERE name = "kb";
JOIN
- A JOIN clause is used to combine rows from two or more tables, based on a related column between them. In MongoDB, joins are not natively supported like in relational databases. Instead, you typically use aggregation pipelines like $lookup for similar functionality.
User.deleteOne({ _id: 1 }) // All users whose name is notKb will be deleted. User.deleteMany({ name: "notKb" })
INNER JOIN
- The INNER JOIN keyword selects records that have matching values in both tables.
DELETE FROM Users WHERE id = 1; DELETE FROM Users WHERE name = "notKb" -- All users whose name is notKb will be deleted.
LEFT JOIN
- The LEFT JOIN keyword returns all records from the left table (table1), and the matching records (if any) from the right table (table2).
// Update the UserSchema to add the 'age' field const UserSchema = new mongoose.Schema({ name: String, email: String, age: Number, // New field });
RIGHT JOIN
- The RIGHT JOIN keyword returns all records from the right table (table2), and the matching records (if any) from the left table (table1).
-- Adds an 'age' column to the Users table ALTER TABLE Users ADD age INT; -- Delete 'Email' column from Users table ALTER TABLE Users DROP COLUMN email; -- Makes 'id' column unsigned and auto-incrementing ALTER TABLE Users MODIFY COLUMN id INT UNSIGNED AUTO_INCREMENT;
CROSS JOIN
- The CROSS JOIN keyword returns all records from both tables (table1 and table2).
// DB is created if it doesn't exist mongoose.connect('mongodb://localhost/my_database');
DATATYPES
In MySQL there are three main data types: string, numeric, and date and time. But in MongoDB, there are a variety of data types, but they differ from those in MySQL. MongoDB uses BSON (Binary JSON) to store data, which supports a rich set of data types. Here's a comparison of common data types in MySQL and MongoDB:
String Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
CHAR, VARCHAR | String | Both store textual data. MongoDB's String is analogous to VARCHAR. |
TEXT, TINYTEXT, etc. | String | No separate TEXT type in MongoDB; all textual data is stored as String. |
Numeric Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
INT, SMALLINT, etc. | NumberInt | Represents 32-bit integers. |
BIGINT | NumberLong | Represents 64-bit integers. |
FLOAT, DOUBLE | NumberDouble | Represents floating-point numbers. |
DECIMAL, NUMERIC | String or custom | MongoDB doesn't have an exact equivalent; use String for precision. |
Date and Time Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
DATE | Date | Both store date-only values. |
DATETIME, TIMESTAMP | Date | MongoDB stores both date and time as a Date object. |
TIME | String or custom | MongoDB does not have a direct TIME type; store as String if needed. |
YEAR | String or Int | Represented using String or NumberInt. |
Boolean Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
BOOLEAN, TINYINT(1) | Boolean | Both store true/false values. |
Binary Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
BLOB, TINYBLOB, etc. | BinData | MongoDB's BinData is used for storing binary data like files. |
JSON/Array Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
JSON | Object | MongoDB natively stores JSON-like documents as Object. |
N/A | Array | MongoDB has a native Array type for storing lists of values. |
Other Data Types
MySQL | MongoDB (BSON) | Notes |
---|---|---|
ENUM | String or custom | Use a String field with validation for enumerated values. |
SET | Array | Use an Array to represent sets of values. |
N/A | ObjectId | Unique identifier type in MongoDB, typically used as a primary key. |
N/A | Decimal128 | Used for high-precision decimal numbers in MongoDB. |
PRIMARY KEY
- Ensures that each row in a table has a unique identifier.
// DB is created if it doesn't exist mongoose.connect('mongodb://localhost/my_database');
CREATE DATABASE my_database;
FOREIGN KEY
- Ensures a column's values correspond to values in another table.
mongoose.connect('mongodb://localhost/my_database');
USE my_database;
Data Integrity and Constraints
- NOT NULL: Ensures that a column cannot have NULL values.
mongoose.model('User', UserSchema);
CREATE TABLE Users ( id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100) NOT NULL, email VARCHAR(100) NOT NULL UNIQUE );
- UNIQUE: Ensures that all values in a column are unique.
UserSchema.index({ email: 1 }); // Unnamed Index UserSchema.index({ email: 1 }, { name: 'idx_email' }); // Named Index
-- Syntax: CREATE INDEX index_name ON table_name (column_name); CREATE INDEX idx_email ON Users (email); -- Named Index CREATE INDEX ON Users (email); -- Unnamed Index
- DEFAULT: Assigns a default value to a column if no value is provided.
console.log(UserSchema.paths); // Outputs details about the schema fields and types
DESCRIBE Users;
- CHECK (MySQL 8.0 ): Ensures that the values in a column satisfy a given condition.
// In mongoose its equivalent to .save() or .create(); const newUser = new User({ name: 'John Doe', email: 'john@example.com' }); newUser.save()
INSERT INTO Users (name, email) VALUES ('John Doe', 'john@example.com');
- AUTO_INCREMENT: Automatically generates a unique value for a column, often used for primary keys.
const users = await User.find(); // Fetches all users const { name, email } = await User.findById(1); // Fetches user with id = 1
SELECT * FROM Users; -- all users SELECT name, email FROM Users WHERE id = 1; -- user of id 1
That's all. You are good to go feel free to leave your feedback and you can get in touch with me here: thekbbohara
OH, by the way how do we setup Mysql.
I recommend using docker:
// update all user of name kb const query = { name: "kb" }; User.update(query, { name: "thekbbohara" })
-- update all user of name kb UPDATE Users SET name = "thekbbohara", email = "thekbbohara@gmail.com" WHERE name = "kb";
The above is the detailed content of Mysql for Mongoose developer.. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
