WordPress新手咨询：能否同时使用自带数据库与旧餐厅菜单数据库？

Absolutely! This is a totally valid approach, and it’s actually pretty common when migrating legacy site content to WordPress while wanting to retain existing structured data (like your restaurant menu database). Here’s how to pull it off smoothly:

Key Approaches to Connect the Two Databases #

1. Direct Custom Database Queries #

You can write simple PHP code (either in a child theme’s functions.php file or a lightweight custom plugin) to connect to your old database and fetch menu data. WordPress’s built-in wpdb class makes this straightforward. Here’s a quick example:

// Define your legacy database credentials (better to put these in wp-config.php as constants!)
$legacy_db = new wpdb('LEGACY_DB_USER', 'LEGACY_DB_PASS', 'LEGACY_DB_NAME', 'LEGACY_DB_HOST');

// Fetch menu items from your old table
$menu_items = $legacy_db->get_results("SELECT item_name, description, price FROM your_menu_table");

// Display the data in your WordPress template
if ($menu_items) {
    echo '<div class="restaurant-menu">';
    foreach ($menu_items as $item) {
        echo '<div class="menu-item">';
        echo '<h3>' . esc_html($item->item_name) . '</h3>';
        echo '<p>' . esc_html($item->description) . '</p>';
        echo '<span class="price">$' . esc_html($item->price) . '</span>';
        echo '</div>';
    }
    echo '</div>';
}

Always sanitize output (like using esc_html()) to avoid security risks, and store your legacy DB credentials as constants in wp-config.php instead of hardcoding them directly in theme files.

2. One-Time Import + Custom Post Type (CPT) #

If you want to eventually merge your menu data into WordPress’s database (to simplify long-term maintenance), create a Menu Item custom post type first. Then write a one-time import script to pull data from your legacy DB into WordPress’s CPT. This lets you use all of WordPress’s built-in features (like editing, categorizing, or adding images to menu items) while phasing out the old database over time.

3. Leverage WordPress’s Database Abstraction #

The wpdb class handles most of the compatibility and security heavy lifting for multiple database connections, so you don’t have to build everything from scratch. It’s beginner-friendly and integrates seamlessly with WordPress’s ecosystem.

Critical Things to Keep in Mind #

• Security: Never expose your database credentials. Define them in wp-config.php like this:

  define('LEGACY_DB_USER', 'your_actual_user');
  define('LEGACY_DB_PASS', 'your_actual_password');
  define('LEGACY_DB_NAME', 'your_legacy_db_name');
  define('LEGACY_DB_HOST', 'localhost');
  

  Then reference these constants in your code.
• Performance: If your menu has hundreds of items, use WordPress’s Transients API to cache query results—this avoids hitting the legacy database on every page load.
• Long-Term Maintenance: Running two databases means double the work for backups, updates, and security checks. If possible, plan a gradual migration to WordPress’s database to simplify your workflow down the line.

Final Thoughts #

You’ve got this! Starting with direct queries is a great way to get your menu up and running quickly while you decide if full migration is right for you. Just test your code in a staging environment first, and don’t hesitate to tweak things as you go.

内容的提问来源于stack exchange，提问作者Joe Estephan