Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Composite key class relationship → ERROR: not mapped to a single property

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
CVariacaoTO class has a composite key (FK_T, FK_F, FK_F_VARIACAO). (FK_F, FK_F_VARIACAO) are also foreign key to FVariacaoTO table, in a ManyToOne relationship.



FVariacaoTO class has two primary keys, into a @Embeddable class FVariacaoPK.

This ERROR has ocurred: referencedColumnNames(FK_F, ID) of CVariacaoTO.fVariacaoTO not mapped to a single property

Relationship is just described in CVariacaoTO class. I don't know if a need write something about relationship in FVariacaoTO class, making @OneToMany or something like that.

What usually done this error?
How usually is done this kind of relationship?
 
Don't destroy the earth! That's where I keep all my stuff! Including this tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
https://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic