Databases
StackOverflow2013
Postsdbo
POCan't create composite primary key with foreign key in PLAY 2.0
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't create composite primary key with foreign key in PLAY 2.0
    primarykey
    data
    text
    <p>This is a situation I want to represent in my PLAY project:</p> <pre><code>table clients { client_id (pk), description } table items { client_id (fk, pk), item_id (pk) } </code></pre> <p>In the 'items' table I want to have a composite primary key that will consist of combined client_id and item_id. I have read JPA documentation as well as many posts on the topic but everything fails again and again. This is one of many versions I have tried - closest to the JPA documentation.</p> <pre><code>@Entity @Table(name = "items") public class Items extends Model { ItemsPK primaryKey; public Items() { } @EmbeddedId public ItemsPK getPrimaryKey() { return primaryKey; } public void setPrimaryKey(ItemsPK pk) { primaryKey = pk; } } @Embeddable public class ItemsPK implements Serializable { private long itemId; private Client client; public ItemsPK() { } @Column(name = "item_id") @GeneratedValue(strategy = GenerationType.AUTO) public long getItemId() { return itemId; } public void setItemId(long itemId) { this.itemId = itemId; } @ManyToOne @JoinColumn(name = "client_id", nullable = false) public Client getClient() { return client; } public void setClient(Client client) { this.client = client; } //public int hashCode() {... //public boolean equals(Object obj) {... } </code></pre> <p>The above code (as well as many other different setups) produce following error during play launch:</p> <blockquote> <p>java.lang.RuntimeException: Error reading annotations for models.ItemsPK at com.avaje.ebeaninternal.server.deploy.parse.ReadAnnotations.readAssociations(ReadAnnotations.java:73) ~[ebean.jar:na] at com.avaje.ebeaninternal.server.deploy.BeanDescriptorManager.readDeployAssociations(BeanDescriptorManager.java:1100) ~[ebean.jar:na]</p> </blockquote> <p>I don't have a clue what might be wrong with my code. I'm starting to think that it is a PLAY bug. Any ideas?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGlenPeterson
    1. USGrzywa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have a solid reason to insist on composite PK? Even if you manage to handle this one, you may face several other problems because of this. Why not add an additional column (say items_id) to items table and put a unique index on (client_id, item_id). (I suppose item_id refers to item table just as client_id refers to clients table).
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. USbpgergo
    2. CO@bpgergo Thank You for Your answer. Your solution is acceptable, but I would rather avoid additional column and index. It surprises me that such a simple case needs to be worked around. If no resolution will appear in a few days I'll reconsider. As for the item_id, currently it is not referencing any other tables, but that might change in the future.
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. USGrzywa
    3. COtags: hibernate** are incorrect here. there is no Hibernate nor JPA
      singulars
      1. POCan't create composite primary key with foreign key in PLAY 2.0
      1. USses
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload