Member Avatar for ElegantElephant

I have the following file called config.php. These are configuration options for a client management system. I need these settings to be editable via the system admin panel. How would I go about storing these values in a database? Would it make sense to have a table called "config" with only one row?

<?php

// System Settings

$system_status = 0; // 0 for active, 1 for locked
$system_status_msg = 'The system is currently inactive. One Aministrators can log in.'; // Modifiable message for when the system as been disabled
$admin_email = 'mk@simplisticstyle.com'; // Set administrator email for PHP Mail Function
$site_url = 'http://localhost'; // Set root location of system
$client_max_upload = 2*1024*1024; // Maximum upload file size for clients
$staff_max_upload = 100*1024*1024; // Maximum upload file size for staff
$contract_max_upload = 5*1024*1024;
$invoice_max_upload = 5*1024*1024;


// Form Validation Settings

$pw_min = 5;

?>
  • 3 Contributors
  • 3 Replies
  • 115 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by ElegantElephant

Dani AI

Generated

Short answer: avoid a single-column, single-row table unless the schema truly never changes. As pointed out, a row-per-setting approach is much more flexible for an editable admin UI; and, as noted, PHP define() constants are fine only when values are static and not editable at runtime.

Recommended pattern: a key/value settings table with type and metadata. That keeps schema changes out of the database DDL and makes the admin UI and migrations simpler.

Example schema (MySQL-friendly):

CREATE TABLE settings (
  name VARCHAR(100) PRIMARY KEY,
  value TEXT NOT NULL,
  type VARCHAR(20) DEFAULT 'string',
  description TEXT,
  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
);

Basic loader pattern (fetch once, then cache for the request or in-memory store): read all rows into an associative array, cast type (int, bool, json) as needed, and use that array throughout the app. For per-client overrides add a user_id or scope column and read global settings first, then merge with user-specific rows.

Practical tips and pitfalls:

  • Store numeric limits (upload sizes) as integers (bytes) and validate ranges on input.
  • If you need flexible nested settings and your DB supports JSON (MySQL 5.7+, PostgreSQL), a JSON column is convenient and searchable; otherwise keep values as typed strings and cast in PHP.
  • Wrap multi-setting edits in a transaction to avoid partial updates.
  • Cache settings (APCu, memcached, or a generated PHP file) so you don’t hit the DB on every request.
  • Sanitize admin-provided strings (especially messages that may contain HTML) and restrict edit access to admins.

This approach balances editability, performance, and future changes better than a single-row table.

Recommended Answers

All 3 Replies

Member Avatar for saiprem

Why do you want to put all those config options in one row in a table, Instead you can create a table config and add a row for each config, this would make easier to edit the code in later.

Member Avatar for phpbeginners

if it only one configuration better use define() the constant value.

But if it is editable and you have a lots of clients with different configurations you have to search every username of the clients and apply each row configuration. Meaning your table is not only one row your table is a multiple rows of multiple users.

Member Avatar for ElegantElephant

Ahh that makes more sense thanks guys. I never thought of it that way, lol

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.