Home/ Questions/Q 8115553
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T03:30:49+00:00

I am trying to create a @OneToMany relationship in JPA using the following table

  • 0

I am trying to create a @OneToMany relationship in JPA using the following table structure.

+----------------+
| CATALOG        |
+----------------+
| catalogId : PK |
| name           |
+----------------+
      |
+----------------+
| PRODUCT        |
+----------------+
| productId : PK |
| name           |
| catalogId : FK |
+----------------+

I have defined the classes as 

@Entity
public class Catalog {
    @Id
    @GeneratedValue
    long catalogId;

    @OneToMany(cascade = CascadeType.ALL, 
               orphanRemoval = true, fetch = FetchType.LAZY)
    @JoinColumn(name = "catalogId", 
               nullable = false, insertable = true, updatable = true)
    Set<Product> products = new HashSet<>();

    String name;
}

@Entity
public class Product {
    @Id
    @GeneratedValue
    long productId;

    String name;
}

However, when I try to persist the catalog object, EclipseLink does not put in the catalogId value as expected and I get a SQL constraint violation that there is a null.

Also, I don’t need nor want a @ManyToOne on the Product end.

The persistence code:

final Catalog catalog = new Catalog();
catalog.name = text;
final Product p = new Product();
p.name = text;
catalog.products.add(p);
em.persist(catalog);

The stack trace:

javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: Column 'CATALOGID'  cannot accept a NULL value.
    at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1367)
    at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1295)
    at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1301)
    at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:866)
    at net.trajano.maven_jee6.ws_mdb_ejb_web.TextMessages.putText(TextMessages.java:61)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When you give ownership of a column on one table, Product, to a different entity, Catalog, that column is going to be updated and maintained as part of persisting Catalog, not as part of persisting Product. The framework is going to create a product, but then because the FK column is “owned” by a different entity, it’s going to populate that with a separate update statement that is generated when the Catalog is persisted. You need to either make the column nullable or put ownership of the column on the same entity that maps the table.

    • 0