How to annotate MYSQL autoincrement field with JPA annotations

by

To use a MySQL AUTO_INCREMENT column, you are supposed to use an IDENTITY strategy:

@Id @GeneratedValue(strategy=GenerationType.IDENTITY)
private Long id;

Which is what you’d get when using AUTO with MySQL:

@Id @GeneratedValue(strategy=GenerationType.AUTO)
private Long id;

Which is actually equivalent to

@Id @GeneratedValue
private Long id;

In other words, your mapping should work. But Hibernate should omit the id column in the SQL insert statement, and it is not. There must be a kind of mismatch somewhere.

Did you specify a MySQL dialect in your Hibernate configuration (probably MySQL5InnoDBDialect or MySQL5Dialect depending on the engine you’re using)?

Also, who created the table? Can you show the corresponding DDL?

Follow-up: I can’t reproduce your problem. Using the code of your entity and your DDL, Hibernate generates the following (expected) SQL with MySQL:

insert 
into
    Operator
    (active, password, username) 
values
    (?, ?, ?)

Note that the id column is absent from the above statement, as expected.

To sum up, your code, the table definition and the dialect are correct and coherent, it should work. If it doesn’t for you, maybe something is out of sync (do a clean build, double check the build directory, etc) or something else is just wrong (check the logs for anything suspicious).

Regarding the dialect, the only difference between MySQL5Dialect or MySQL5InnoDBDialect is that the later adds ENGINE=InnoDB to the table objects when generating the DDL. Using one or the other doesn’t change the generated SQL.

More Related Contents:

  1. Hibernate Annotations – Which is better, field or property access?
  2. Do I need elements in persistence.xml?
  3. How to map one class to different tables using hibernate/jpa annotations
  4. How to fix the Hibernate “object references an unsaved transient instance – save the transient instance before flushing” error
  5. How to map calculated properties with JPA and Hibernate
  6. Connection to Db dies after >4
  7. When and why JPA entities should implement the Serializable interface?
  8. Why does JPA have a @Transient annotation?
  9. JPQL Create new Object In Select Statement – avoid or embrace?
  10. How to remove entity with ManyToMany relationship in JPA (and corresponding join table rows)?
  11. Storing a Map using JPA
  12. How to persist a property of type List in JPA?
  13. Hibernate: Automatically creating/updating the db tables based on entity classes
  14. I found JPA, or alike, don’t encourage DAO pattern
  15. Getting Database connection in pure JPA setup
  16. Hibernate – @ElementCollection – Strange delete/insert behavior
  17. Hibernate/JPA – annotating bean methods vs fields [duplicate]
  18. How to clone a JPA entity
  19. Is it possible to dynamically define column names in Hibernate / JPA?
  20. How to use Hibernate @Any-related annotations?
  21. @Basic(optional = false) vs @Column(nullable = false) in JPA
  22. No operator matches the given name and argument type(s). You might need to add explicit type casts. — Netbeans, Postgresql 8.4 and Glassfish
  23. Batch inserts with JPA/EJB3
  24. Hibernate triggering constraint violations using orphanRemoval
  25. Hibernate vs JPA vs JDO – pros and cons of each? [closed]
  26. What is Persistence Context?
  27. Clarifying terminology – What does “hydrating” a JPA or Hibernate entity mean when fetching the entity from the DB
  28. Setting a JPA timestamp column to be generated by the database?
  29. JPA Criteria Tutorial [closed]
  30. Does JPA support mapping to sql views?

Leave a Comment