javax.persistence

Annotation Type OrderBy


  • @Target(value={METHOD,FIELD})
     @Retention(value=RUNTIME)
    public @interface OrderBy
    Specifies the ordering of the elements of a collection valued association or element collection at the point when the association or collection is retrieved.

    The syntax of the value ordering element is an orderby_list, as follows:

        orderby_list::= orderby_item [,orderby_item]*
        orderby_item::= [property_or_field_name] [ASC | DESC]
     

    If ASC or DESC is not specified, ASC (ascending order) is assumed.

    If the ordering element is not specified for an entity association, ordering by the primary key of the associated entity is assumed.

    The property or field name must correspond to that of a persistent property or field of the associated class or embedded class within it. The properties or fields used in the ordering must correspond to columns for which comparison operators are supported.

    The dot (".") notation is used to refer to an attribute within an embedded attribute. The value of each identifier used with the dot notation is the name of the respective embedded field or property.

    The OrderBy annotation may be applied to an element collection. When OrderBy is applied to an element collection of basic type, the ordering will be by value of the basic objects and the property or field name is not used. When specifying an ordering over an element collection of embeddable type, the dot notation must be used to specify the attribute or attributes that determine the ordering.

    The OrderBy annotation is not used when an order column is specified.

        Example 1:
        
        @Entity 
        public class Course {
           ...
           @ManyToMany
           @OrderBy("lastname ASC")
           public List<Student> getStudents() {...};
           ...
        }
        
        Example 2:
    
        @Entity 
        public class Student {
           ...
           @ManyToMany(mappedBy="students")
           @OrderBy // ordering by primary key is assumed
           public List<Course> getCourses() {...};
           ...
        }
    
        Example 3: 
    
        @Entity 
        public class Person {
             ...
           @ElementCollection
           @OrderBy("zipcode.zip, zipcode.plusFour")
           public Set<Address> getResidences() {...};
           ...
        }
      
        @Embeddable 
        public class Address {
           protected String street;
           protected String city;
           protected String state;
           @Embedded protected Zipcode zipcode;
        }
    
        @Embeddable 
        public class Zipcode {
           protected String zip;
           protected String plusFour;
        }
     
    Since:
    Java Persistence 1.0
    See Also:
    OrderColumn
    • Element Detail

      • value

        public abstract String value
        An orderby_list. Specified as follows:
            orderby_list::= orderby_item [,orderby_item]*
            orderby_item::= [property_or_field_name] [ASC | DESC]
         

        If ASC or DESC is not specified, ASC (ascending order) is assumed.

        If the ordering element is not specified, ordering by the primary key of the associated entity is assumed.

        Default:
        ""

Document created the 11/06/2005, last modified the 18/08/2025
Source of the printed document:https://www.gaudry.be/en/java-api-javaee-rf-javax/persistence/OrderBy.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author of this site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.