What are the best practices for separating database connection logic from email content generation in PHP scripts?

To separate database connection logic from email content generation in PHP scripts, it is recommended to create separate functions or classes for each task. This helps in keeping the code modular, easy to maintain, and improves code readability. By encapsulating database connection logic in one function or class and email content generation in another, it becomes easier to make changes or updates to each part independently. 

// Function to establish a database connection
function connectToDatabase() {
    $dbHost = 'localhost';
    $dbUser = 'username';
    $dbPass = 'password';
    $dbName = 'database_name';
    
    $conn = new mysqli($dbHost, $dbUser, $dbPass, $dbName);
    
    if ($conn->connect_error) {
        die("Connection failed: " . $conn->connect_error);
    }
    
    return $conn;
}

// Function to generate email content
function generateEmailContent($name, $message) {
    $emailContent = "Hello $name,\n\n";
    $emailContent .= "Here is the message you sent: $message\n\n";
    $emailContent .= "Thank you!";
    
    return $emailContent;
}

// Example of using the functions
$conn = connectToDatabase();
$emailContent = generateEmailContent("John", "Hello, this is a test message.");

// Send email with $emailContent

Keywords

database connection email generation separation of concerns PHP scripts best practices

Related Questions