


Building a PHP CRUD Application with OOP and MySQL: A Best Practice Guide
Jan 11, 2025 am 07:20 AMEfficiently managing database operations is crucial for PHP application development. CRUD (Create, Read, Update, Delete) is one of the most common database operations. Adopting object-oriented programming (OOP) principles can help make your code simpler and easier to reuse and extend. Using MySQL with PHP also ensures that your application can handle data storage efficiently.
This blog post will walk you through how to build a PHP CRUD application using OOP and MySQL. We'll follow best practices and design patterns to organize the code so that it's beginner-friendly yet powerful enough to be used on larger projects.
After reading this guide, you will have a solid foundation for working with databases using OOP principles in PHP.
Table of Contents
- The importance of OOP in PHP
- Project Settings
- Create database
- Folder structure
- Connect to database
- Create CRUD operations
- Create
- Read
- Update
- Delete
- Summary
1. The importance of OOP in PHP
Object-oriented programming (OOP) is a programming paradigm that uses "objects" to organize code. In PHP, OOP allows you to create classes that represent real-world entities, making your code more modular, easier to reuse, and easier to manage.
Applying OOP principles when working with databases means:
- Separation of Concerns: Database logic is encapsulated in a class, separate from the rest of the application logic.
- Reusability: You can reuse database classes in multiple parts of your application.
- Maintainability: As your application grows, your code is easier to update and extend.
2. Project settings
Before we start coding, let’s set up an easy-to-maintain folder structure. Your project should be organized as follows:
<code>php-crud/ ├── config/ │ └── Database.php ├── controllers/ │ └── UserController.php ├── models/ │ └── User.php ├── views/ │ └── user_list.php ├── public/ │ └── index.php └── .gitignore</code>
- config/Database.php: Contains database connection logic.
- controllers/UserController.php: Handles CRUD operations and communicates with the model.
- models/User.php: Contains logic for interacting with the users table in MySQL.
- views/user_list.php: Display user data in table form.
- public/index.php: The entry point of the application.
3. Create database
Let’s start by creating the database and users table in MySQL. You can execute the following SQL query to set up the database:
CREATE DATABASE php_crud; USE php_crud; CREATE TABLE users ( id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100) NOT NULL, email VARCHAR(100) NOT NULL, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP );
This table will store basic user information such as name, email, and creation date.
4. Folder structure
We have set up the basic folder structure. Here's a breakdown of what each folder does:
- config/: Contains database configuration and connection logic.
- controllers/: Handle the request and call the corresponding method in the model.
- models/: Represents business logic and database interaction.
- views/: Display data to the user.
- public/: The public folder contains the index.php file, which will serve as the entry point to the application.
5. Connect to database
Let’s start by creating a database connection class in config/Database.php:
<code>php-crud/ ├── config/ │ └── Database.php ├── controllers/ │ └── UserController.php ├── models/ │ └── User.php ├── views/ │ └── user_list.php ├── public/ │ └── index.php └── .gitignore</code>
This class creates a PDO connection to MySQL and is reusable in your project.
6. Create CRUD operations
Let’s create a model for handling user data. This class will interact with the users table and perform CRUD operations.
Create model (User.php)
CREATE DATABASE php_crud; USE php_crud; CREATE TABLE users ( id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100) NOT NULL, email VARCHAR(100) NOT NULL, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP );
Create Controller (UserController.php)
<?php namespace Config; use PDO; class Database { private $host = '127.0.0.1'; private $dbName = 'php_crud'; private $username = 'root'; private $password = ''; private $connection; public function connect() { try { $this->connection = new PDO( "mysql:host={$this->host};dbname={$this->dbName}", $this->username, $this->password ); $this->connection->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); return $this->connection; } catch (PDOException $e) { die("Database connection failed: " . $e->getMessage()); } } }
Create view (user_list.php)
<?php namespace Models; use Config\Database; class User { private $conn; public function __construct() { $database = new Database(); $this->conn = $database->connect(); } public function create($name, $email) { $sql = "INSERT INTO users (name, email) VALUES (:name, :email)"; $stmt = $this->conn->prepare($sql); $stmt->bindParam(':name', $name); $stmt->bindParam(':email', $email); return $stmt->execute(); } public function read() { $sql = "SELECT * FROM users"; $stmt = $this->conn->prepare($sql); $stmt->execute(); return $stmt->fetchAll(\PDO::FETCH_ASSOC); } public function update($id, $name, $email) { $sql = "UPDATE users SET name = :name, email = :email WHERE id = :id"; $stmt = $this->conn->prepare($sql); $stmt->bindParam(':name', $name); $stmt->bindParam(':email', $email); $stmt->bindParam(':id', $id); return $stmt->execute(); } public function delete($id) { $sql = "DELETE FROM users WHERE id = :id"; $stmt = $this->conn->prepare($sql); $stmt->bindParam(':id', $id); return $stmt->execute(); } }
Create entry point (index.php)
<?php namespace Controllers; use Models\User; class UserController { public function createUser($name, $email) { $user = new User(); return $user->create($name, $email); } public function getUsers() { $user = new User(); return $user->read(); } public function updateUser($id, $name, $email) { $user = new User(); return $user->update($id, $name, $email); } public function deleteUser($id) { $user = new User(); return $user->delete($id); } }
Summary
By following OOP principles and applying best practices in PHP, we built a simple and scalable CRUD application. This approach allows you to easily extend your project with new functionality or improve database interaction.
In this guide, we cover:
- Simple and easy to maintain folder structure.
- Reusable Database class for MySQL connections.
- User model that encapsulates all CRUD operations.
- UserController for handling business logic.
This structure makes your PHP applications cleaner, more modular, and easier to extend. You can now use this approach to build larger, more complex applications using OOP and MySQL.
Happy coding! ?
The above is the detailed content of Building a PHP CRUD Application with OOP and MySQL: A Best Practice Guide. 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

The default user name of MySQL is usually 'root', but the password varies according to the installation environment; in some Linux distributions, the root account may be authenticated by auth_socket plug-in and cannot log in with the password; when installing tools such as XAMPP or WAMP under Windows, root users usually have no password or use common passwords such as root, mysql, etc.; if you forget the password, you can reset it by stopping the MySQL service, starting in --skip-grant-tables mode, updating the mysql.user table to set a new password and restarting the service; note that the MySQL8.0 version requires additional authentication plug-ins.

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.

There are three ways to modify or reset MySQLroot user password: 1. Use the ALTERUSER command to modify existing passwords, and execute the corresponding statement after logging in; 2. If you forget your password, you need to stop the service and start it in --skip-grant-tables mode before modifying; 3. The mysqladmin command can be used to modify it directly by modifying it. Each method is suitable for different scenarios and the operation sequence must not be messed up. After the modification is completed, verification must be made and permission protection must be paid attention to.

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

InnoDB implements repeatable reads through MVCC and gap lock. MVCC realizes consistent reading through snapshots, and the transaction query results remain unchanged after multiple transactions; gap lock prevents other transactions from inserting data and avoids phantom reading. For example, transaction A first query gets a value of 100, transaction B is modified to 200 and submitted, A is still 100 in query again; and when performing scope query, gap lock prevents other transactions from inserting records. In addition, non-unique index scans may add gap locks by default, and primary key or unique index equivalent queries may not be added, and gap locks can be cancelled by reducing isolation levels or explicit lock control.

Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi

The function of InnoDBBufferPool is to improve MySQL read and write performance. It reduces disk I/O operations by cacheing frequently accessed data and indexes into memory, thereby speeding up query speed and optimizing write operations; 1. The larger the BufferPool, the more data is cached, and the higher the hit rate, which directly affects database performance; 2. It not only caches data pages, but also caches index structures such as B-tree nodes to speed up searches; 3. Supports cache "dirty pages", delays writing to disk, reduces I/O and improves write performance; 4. It is recommended to set it to 50%~80% of physical memory during configuration to avoid triggering swap; 5. It can be dynamically resized through innodb_buffer_pool_size, without restarting the instance.
