EntityManager persist multiple relationship - spring-boot

Question

I have spring boot rest api, I have persisted 1 table successfully, but when I tried to persist object which has 2 another relations and I got error:
o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 1364, SQLState:
HY000
o.h.engine.jdbc.spi.SqlExceptionHelper : Field 'id' doesn't have a default value
here is my entity and entity manger persistance:
#Entity
#Table(name="booking")
public class Booking {
#Id
#GeneratedValue(strategy=GenerationType.AUTO)
#Column(name="id")
private int id;
#Column(name="description")
private String description;
#OneToMany(mappedBy="booking",cascade = CascadeType.ALL)
private List<CategoriesBooking> bookingInfos = new ArrayList<>();
#Entity
#Table(name="category_booking")
public class CategoriesBooking {
#Id
#GeneratedValue(strategy=GenerationType.AUTO)
#Column(name="id")
private int id;
#Column(name = "name")
private String name;
#ManyToOne(fetch=FetchType.LAZY, cascade=CascadeType.ALL)
#JoinColumn(name="booking_id")
private Booking booking;
#OneToMany(mappedBy="categoriesBooking",cascade = CascadeType.ALL)
private List<OptionsBooking> options = new ArrayList<>();
#Entity
#Table(name="options_booking")
public class OptionsBooking {
#Id
#GeneratedValue(strategy=GenerationType.AUTO)
#Column(name="id")
private int id;
#Column(name="name")
private String name;
#ManyToOne(fetch=FetchType.LAZY, cascade=CascadeType.ALL)
#JoinColumn(name = "catebooking_id")
private CategoriesBooking categoriesBooking;
#Transactional
#Repository
public class Services{
#PersistenceContext
protected EntityManager entityManager;
public Services() {
}
public boolean add(Booking booking){
try {
entityManager.persist(booking);
return true;
} catch (Exception e) {
entityManager.getTransaction().rollback();
}
return false;
}
}
data:
{description: 'test for persist',
bookingInfos:[{
name:'test1',
options:[{
name: 'test1-test1'
}]
}]
}
I update for use MySQL

Answer 1

GenerationType.AUTO chooses an ID generation strategy suitable for your database. What it actually picks depends on the database you are using. But judging from the error message it assumes the id column to be some kind of IDENTITY field which creates a unique value upon insertion.
And it seems your schema doesn't declare the id column in this way.
The obvious fix is to change that.

Answer 2

Sometimes changes made to the model or to the ORM may not reflect accurately on the database even after an execution of SchemaUpdate.
If the error actually seems to lack a sensible explanation, try recreating the database (or at least creating a new one) and scaffolding it with SchemaExport.