Hibernate Community • View topic - Why table in @CollectionTable doesn't need a config entry

View unanswered posts | View active topics

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

Why table in @CollectionTable doesn't need a config entry

Page 1 of 1

[ 2 posts ]

Previous topic | Next topic

Author

Message

sumithar

Post subject: Why table in @CollectionTable doesn't need a config entry

Posted: Mon Jun 27, 2016 10:02 pm

Newbie

Joined: Sat Jun 25, 2016 5:58 pm
Posts: 3

So, I have a collection of basic type (String) that corresponds to a child table in the database. In my parent entity class I specify as follows

Code:

@CollectionTable(name="BANK_CONTACT", joinColumns=@JoinColumn(name="BANK_ID"))

Why is it that I don't need an entry for BANK_CONTACT in hibernate.cfg.xml?
Thanks!

Top

vlad

Post subject: Re: Why table in @CollectionTable doesn't need a config entry

Posted: Tue Jun 28, 2016 5:00 am

Hibernate Team

Joined: Thu Sep 11, 2014 2:50 am
Posts: 1628
Location: Romania

@ElementCollection allows you to map value objects, not entities. The underlying table is managed automatically by Hibernate, just like in any unidirectional association.

However, a bidirectional @OneToMany association performs better than any unidirectional collection or @ElementCollection.

Top

Page 1 of 1

[ 2 posts ]

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum