Hibernate提示test.employee表不存在问题求助

Hey there! Let's work through this Hibernate + MySQL issue you're hitting—totally get how confusing this can be when you're just starting out with the framework. Let's break down what's going on and fix it step by step.

First, let's understand the core problem #

You're seeing a Table 'test.employee' doesn't exist error, even when setting hibernate.hbm2ddl.auto to update. Worse, when you manually create the table, Hibernate tries to delete it but claims it doesn't exist. This almost always boils down to table name case sensitivity or mismatched Hibernate dialect for your MySQL version.

Fix 1: Fix Table Name Case Sensitivity (Most Likely Culprit) #

MySQL handles table name case differently depending on your OS:

• On Windows, it's case-insensitive by default (all table names get stored as lowercase)
• On Linux/macOS, it's case-sensitive by default

Your entity uses @Table(name = "EMPLOYEE") (uppercase), but the error references test.employee (lowercase). Here's how to fix this:

• Option 1 (Easiest): Update your entity's @Table annotation to use lowercase:

  @Entity
  @Table(name = "employee") // Lowercase instead of uppercase
  public class Employee {
      // ... rest of your code
  }
  

• Option 2: If you need to keep uppercase table names (Linux/macOS only), modify your MySQL config file (my.cnf or my.ini) to set:

  lower_case_table_names = 1
  

  Then restart MySQL. This will make MySQL store all table names as lowercase, matching what Hibernate is looking for.

Fix 2: Use the Correct Hibernate Dialect for Your MySQL Version #

If you're using MySQL 8.0 or newer, the old MySQLDialect is outdated and can cause DDL generation issues. Update your hibernate.cfg.xml to use the modern dialect:

<property name="hibernate.dialect">org.hibernate.dialect.MySQL8Dialect</property>

This ensures Hibernate generates SQL syntax that's compatible with your MySQL version, which is critical for auto-creating tables.

Fix 3: Verify Permissions and hbm2ddl Behavior #

• Check Database Permissions: Make sure your root user has full permissions on the test database (create, drop, alter tables). Missing permissions can silently fail table creation.
• Enable SQL Logging: You already have hibernate.show_sql=true, so run your program again and check the console for CREATE TABLE statements. If you don't see one, double-check your <mapping class="com.sopra.pojo.Employee" /> line in hibernate.cfg.xml—a typo here means Hibernate won't recognize your entity.
• Test with create-drop: Temporarily set hibernate.hbm2ddl.auto=create-drop, run the program, and check MySQL Workbench immediately after. If the table gets created and then dropped when the program ends, that means the auto-ddl is working (and the original issue was case sensitivity).

Quick Test to Confirm #

After making the above changes, run your EmployeeDBManager again. If Hibernate creates the employee table automatically and inserts your data, you're good to go! If not, check the console for any new error messages—they'll give us more clues.

内容的提问来源于stack exchange，提问作者Salim Shamim