Home/ Questions/Q 6569369
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T14:37:06+00:00

When they appear on a field/getter of an @Entity , what is the difference

  • 0

  1. When they appear on a field/getter of an @Entity, what is the difference between them? (I persist the Entity through Hibernate).

  2. What framework and/or specification each one of them belongs to?

  3. @NotNull is located within javax.validation.constraints. In the javax.validation.constraints.NotNull javadoc it says

    The annotated element must not be null

    but it does not speak of the element’s representation in the database, so why would I add the constraint nullable=false to the column?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    @NotNull is a JSR 303 Bean Validation annotation. It has nothing to do with database constraints itself. As Hibernate is the reference implementation of JSR 303, however, it intelligently picks up on these constraints and translates them into database constraints for you, so you get two for the price of one. @Column(nullable = false) is the JPA way of declaring a column to be not-null. I.e. the former is intended for validation and the latter for indicating database schema details. You’re just getting some extra (and welcome!) help from Hibernate on the validation annotations.

    • 0