Is it best practice to create a new table for each module in a PHP application?

It is not best practice to create a new table for each module in a PHP application. Instead, it is recommended to use a single database table with a column that distinguishes between different modules. This approach helps to keep the database structure simple and manageable, and allows for easier maintenance and scalability. 

// Example of creating a database table with a 'module' column
$servername = "localhost";
$username = "username";
$password = "password";
$dbname = "myDB";

// Create connection
$conn = new mysqli($servername, $username, $password, $dbname);

// Check connection
if ($conn->connect_error) {
    die("Connection failed: " . $conn->connect_error);
}

// SQL query to create a table with a 'module' column
$sql = "CREATE TABLE modules (
    id INT(6) UNSIGNED AUTO_INCREMENT PRIMARY KEY,
    module VARCHAR(30) NOT NULL,
    data TEXT
)";

if ($conn->query($sql) === TRUE) {
    echo "Table created successfully";
} else {
    echo "Error creating table: " . $conn->error;
}

$conn->close();

Keywords

database design table structure modular programming PHP application scalability

Related Questions