Spring Boot+Hibernate多对一关联创建Account时约束违反问题

Alright, let's work through this frustrating issue step by step. I've gone through all your attempts, and the core problems are a mix of misconfigured JPA annotations, incorrect request payloads, and a tiny bit of confusion around how @ManyToOne associations work in Hibernate.

First, quick clarity check: You mentioned "one account can belong to single or multiple users"—but @ManyToOne means multiple accounts belong to one user (one account is linked to exactly one user, many accounts can share the same user). If you actually need an account to link to multiple users, you'd need @ManyToMany, but let's stick with your stated @ManyToOne setup for now.

Why Your Previous Attempts Failed #

Let's break down each error you hit:

• {"name": "some account purpose", "user": 1} → "user_id=1不存在于bankuser表":
  Either the User with ID 1 truly doesn't exist in your bankuser table, OR your User entity isn't mapped to the bankuser table (Hibernate defaults to using the class name, so if your entity is User, it might be looking for a user table instead of bankuser).
• {"name": "some account purpose", "user": "http://localhost:8080/basicbank/user/1"} → JsonMappingException:
  Spring doesn't automatically convert URLs to entity objects unless you set up HATEOAS with entity links—this is overkill for a simple use case.
• {"name": "some account purpose", "user": {"id": 1, "firstname": "joao", "lastname": "pereira"}} → ConstraintViolationException:
  Hibernate treats this as a new User object (not the existing one with ID 1) unless you explicitly fetch it from the database first. It won't automatically recognize the ID as a reference to a persisted user.
• Modified @ManyToOne with insertable=false, updatable=false + {"name": "some account purpose", "user_id": 1} → "user不可为null":
  The insertable=false, updatable=false tells Hibernate not to write to the user_id column. Even if you set the User or pass user_id, Hibernate ignores it—so the column stays null, violating your @NotNull constraint.

Correct Configuration & Fixes #

Step 1: Fix the Account Entity Annotation #

First, clean up your @ManyToOne mapping to let Hibernate properly manage the user_id foreign key:

@Entity
public class Account {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String name;

    @NotNull
    @ManyToOne(fetch = FetchType.LAZY)
    // Match the column name to your database (user_id), and enforce non-null at the DB level
    @JoinColumn(name = "user_id", nullable = false)
    private User user;

    // Getters, setters, no-arg + all-arg constructors
}

Make sure your User entity is mapped to the correct table:

@Entity
@Table(name = "bankuser") // Critical! Matches the table name in your error message
public class User {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String firstname;
    private String lastname;

    // Optional: Add bidirectional association if needed
    // @OneToMany(mappedBy = "user", fetch = FetchType.LAZY)
    // private List<Account> accounts = new ArrayList<>();

    // Getters, setters, constructors
}

Step 2: Use a DTO for Request Payloads (Most Reliable Approach) #

Instead of trying to map JSON directly to your Account entity, use a Data Transfer Object (DTO) to handle the request. This gives you full control over how you associate the User with the Account.

First, create the DTO:

public class AccountCreateRequest {
    private String name;
    private Long userId;

    // Getters and setters
}

Then, update your Controller to fetch the User and bind it to the Account:

@RestController
@RequestMapping("/accounts")
public class AccountController {

    private final AccountService accountService;
    private final UserService userService;

    // Constructor injection (preferred over @Autowired)
    public AccountController(AccountService accountService, UserService userService) {
        this.accountService = accountService;
        this.userService = userService;
    }

    @PostMapping
    public ResponseEntity<Account> createAccount(@RequestBody AccountCreateRequest request) {
        // Fetch the existing User from the database
        User user = userService.findById(request.getUserId())
                .orElseThrow(() -> new RuntimeException("User not found with ID: " + request.getUserId()));

        // Create and populate the Account entity
        Account account = new Account();
        account.setName(request.getName());
        account.setUser(user);

        // Save and return the account
        Account savedAccount = accountService.save(account);
        return ResponseEntity.ok(savedAccount);
    }
}

Step 3: Send the Correct Request #

Now send this JSON payload via Postman:

{"name": "some account purpose", "userId": 1}

Important: Double-check that a User with ID 1 actually exists in your bankuser table—this was likely the root cause of your first error.

Alternative: Let Spring Automatically Map the User ID (Optional) #

If you want to skip the DTO, you can add a constructor to your User entity that accepts only the ID, and configure Jackson to use it:

public class User {
    // ... existing fields ...

    // Constructor for Jackson to map ID to User reference
    public User(Long id) {
        this.id = id;
    }

    // Don't forget the no-arg constructor (required by Hibernate)
    public User() {}

    // ... getters/setters ...
}

Then you can send this payload:

{"name": "some account purpose", "user": {"id": 1}}

Hibernate will recognize this as a reference to an existing User (instead of a new one) when saving the Account.

内容的提问来源于stack exchange，提问作者Jim C