What are the potential pitfalls of switching from procedural to OOP MySQL in PHP?

One potential pitfall of switching from procedural to OOP MySQL in PHP is the need to refactor existing code to adhere to OOP principles, which can be time-consuming. Additionally, developers may need to learn new syntax and concepts related to OOP, which can lead to a learning curve. It is important to plan and allocate enough time for the transition to ensure a smooth migration process. 

// Example of refactoring procedural MySQL code to OOP MySQL code

// Procedural MySQL code
$conn = mysqli_connect('localhost', 'username', 'password', 'database');
$result = mysqli_query($conn, "SELECT * FROM table");
while ($row = mysqli_fetch_assoc($result)) {
    echo $row['column'];
}
mysqli_close($conn);

// OOP MySQL code
class Database {
    private $conn;
    
    public function __construct($host, $username, $password, $database) {
        $this->conn = new mysqli($host, $username, $password, $database);
    }
    
    public function query($sql) {
        return $this->conn->query($sql);
    }
    
    public function fetchAssoc($result) {
        return $result->fetch_assoc();
    }
    
    public function close() {
        $this->conn->close();
    }
}

$db = new Database('localhost', 'username', 'password', 'database');
$result = $db->query("SELECT * FROM table");
while ($row = $db->fetchAssoc($result)) {
    echo $row['column'];
}
$db->close();

Keywords

MySQL PHP procedural OOP migration

Related Questions