Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You place them either on the <em>field</em> or on the <em>getter</em>. From the Hibernate Annotations Reference Guide:</p> <blockquote> <h2><a href="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/#entity-mapping-entity" rel="nofollow noreferrer">2.2.1. Marking a POJO as persistent entity</a></h2> <p>(...)</p> <p>Depending on whether you annotate fields or methods, the access type used by Hibernate will be field or property. The EJB3 spec requires that you declare annotations on the element type that will be accessed, i.e. the getter method if you use property access, the field if you use field access. Mixing annotations in both fields and methods should be avoided. Hibernate will guess the access type from the position of @Id or @EmbeddedId.</p> </blockquote> <p>You might also want to read about the <code>@Access</code> annotation that allows to force/override the access type (prior to Hibernate Annotations 3.5 and JPA 2.0, it was part of Hibernate Annotation Extensions):</p> <blockquote> <h3><a href="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/#d0e535" rel="nofollow noreferrer">2.2.2.2. Access type</a></h3> <p>By default the access type of a class hierarchy is defined by the position of the @Id or @EmbeddedId annotations. If these annotations are on a field, then only fields are considered for persistence and the state is accessed via the field. If there annotations are on a getter, then only the getters are considered for persistence and the state is accessed via the getter/setter. That works well in practice and is the recommended approach.</p> <blockquote> <p><strong>Note</strong></p> <p>The placement of annotations within a class hierarchy has to be consistent (either field or on property) to be able to determine the default access type. It is recommended to stick to one single annotation placement strategy throughout your whole application.</p> </blockquote> <p>However in some situations, you need to:</p> <ul> <li>force the access type of the entity hierarchy</li> <li>override the access type of a specific entity in the class hierarchy</li> <li>override the access type of an embeddable type</li> </ul> <p>The best use case is an embeddable class used by several entities that might not use the same access type. In this case it is better to force the access type at the embeddable class level.</p> <p>(...)</p> </blockquote> <p>Regarding the pros and cons of both styles, I suggest to read the following questions:</p> <ul> <li><a href="https://stackoverflow.com/questions/942035/hibernate-jpa-annotating-bean-methods-vs-fields">Hibernate/JPA - annotating bean methods vs fields</a></li> <li><a href="https://stackoverflow.com/questions/594597/hibernate-annotations-which-is-better-field-or-property-access">Hibernate Annotations - Which is better, field or property access?</a></li> <li><a href="https://stackoverflow.com/questions/332591/performance-difference-between-annotating-fields-or-getter-methods-in-hibernate">Performance difference between annotating fields or getter methods in Hibernate / JPA</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWhere to put hibernate annotations?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPascal Thivent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhere to put hibernate annotations?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo are you saying that if i put the annotations on the fields, then the get/setters will not be used for anything? What about simple (eg string) fields that don't need annotations, will their fields or setters be used?
      singulars
      1. PO
      1. USChris
    2. CO@Chris: If you use field access, *Hibernate* will bypass the get/set pair and access the field directly, using reflection. Regarding the second part of your comment, it all depends on the access type - field or property - that will be guessed *from the position of @Id or @EmbeddedId*.
      singulars
      1. PO
      1. USPascal Thivent
    3. COI've since found that if i use field access, i run into all sorts of problems with the proxies that Hibernate uses for lazy loading. So getters/setters it is! Woo hoo code generation to the rescue! Damn this java stuff is verbose!
      singulars
      1. PO
      1. USChris
 

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