ObjectDB Database Search

1-24 of 24 results

ORDER BY clause (JPQL / Criteria API)

clause . Order Direction ( ASC , DESC) The default ordering direction is ascending ... follows: SELECT c.name FROM Country c ORDER BY c.name ASC On the other hand, to apply descending order ... ); Root c = q. from (Country.class); q. select (c); q. orderBy (cb. asc (c. get ("currency")), cb. desc

CriteriaBuilder.asc(x) - JPA Method

JPA Method in javax.persistence.criteria.CriteriaBuilder Order asc (    Expression  x ) Create an ordering by the ascending value of the expression. Parameters: x - expression used to define the ordering Return: ascending ordering corresponding to the expression Since: JPA 2.0

Criteria Query Selection and Results

interface is a thin wrapper around Expression , which adds order direction - either ascending ( ASC ) or descending (DESC). The CriteriaBuilder 's asc and desc methods take an expression and return

ObjectDB Object Database Features

and aggregates ). ORDER BY (including ASC , DESC). Aggregates (COUNT, SUM, AVG, MAX, MIN). Query

JPA Query Structure (JPQL / Criteria)

, ...). Criteria ORDER BY  ( orderBy , Order , asc , desc ).

FROM clause (JPQL / Criteria API)

but cannot be one of the following reserved words: ABS, ALL, AND, ANY, AS, ASC , AVG, BETWEEN, BIT_LENGTH, BOTH, BY, CASE

JPA Criteria API Queries

clause ( orderBy , Order , asc , desc ). The links above are direct links to the criteria query

javax.persistence.OrderBy

] [ ASC | DESC] If ASC or DESC is not specified, ASC (ascending order) is assumed. If the ordering ... @OrderBy("lastname ASC ") public List getStudents() {...}; ... } Example 2: @Entity public class Student ... _or_field_name] [ ASC | DESC] If ASC or DESC is not specified, ASC (ascending order) is assumed

Cannot sort descending, when ordering by caluculated float in a method

this query: (I know, it's not very efficient...) select i from Invoice i order by i.getPrice() desc/ asc it gives the same order for desc and asc (every time asc ) When the float is not calculated (only returned ... in this case at all - it was only a luck, that asc ordering was working... anaq x Following

Listing large number of complicated objects with paging.

with such a simple query: select prod from Product prod order by prod.id ASC Right now I have 55541 ... ("select prod from Product prod order by prod.id ASC ", Product.class); prodList = icQuery ... order by prod.id ASC ] 2011-11-15 19:30:59.578 [http-bio-8080-exec-3] DEBUG pl.hplxtool.dao.impl

Problem with distinct select, order by and equivalent alias/attribute path

;  + "order by s_location.id asc ";         ... ;  + "order by s.location.id asc ";         ... ;   + "order by s_location.id asc ";        

javax.persistence.Index

follows: column::= index_column [,index_column] index_column::= column_name [ ASC | DESC] If ASC or DESC is not specified, ASC (ascending order) is assumed. See Also: Table SecondaryTable

javax.persistence.OrderBy.value

JPA Annotation Attribute in javax.persistence.OrderBy String value default "" 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

NULL prefered in ORDER BY?

do something like SELECT FROM Test ORDER BY hint.name It orders ASC like this (assuming I've got ... though what I want for ASC (because it simply makes more sense) is: Test 1 (with hint = A) Test 2 (with hint

How to convert a boolean to an int in the query?

;  q.select(intCaptial);         q.orderBy(cb. asc (intCaptial ... .as(Integer.class); q.select(intApproveEmail); q.orderBy(cb. asc (intApproveEmail)); query = em

order by string with numbers

  The sql that works is ORDER BY CAST(SUBSTR(username FROM 4) AS UNSIGNED) ASC Using JPQL SELECT u FROM Users u ORDER BY SUBSTRING(u.username,4)*1 ASC If you have other alternative for JPA

javax.persistence.criteria.CriteriaBuilder

- if an argument is a tuple- or array-valued selection item Since: JPA 2.0 Order asc ( Expression  

Query perfromance problem

+ " ASC ";    } else {     q = "select prod from Product prod order by prod

Grouping by date()

hour(ov.created) ASC where ov.created is normal Date() field return only hours from 0 to 11 (check

Attempt to open a non existing file '/tmp/objectdb_xxxx/SortQueryItr_6.mrg'

bk FROM OBN bk ORDER BY bk.time ASC ", OBN); ) 2/ after a little while - some of the applications

Get the last occurence of a list attribut

.persistenceId ASC But it's look like it's not a correct query, the compiler does not like the parentheses

Sort of very large objects - out of memory

with different ASC / DESC components will be supported in future versions. Meanwhile, consider reversing

Alias not used in ORDER BY

Hi, I am doing something simple like final Root from = criteria.from(T.class) final Path path = from.get("someStringProperty") final Expression upperPath = builder.upper((Expression ) path); upperPath.alias("TEST"); criteria.multiselect(from, path); criteria.orderBy(builder. asc (upperPath)) I

Strange Error with Criteria API and Sorting

= root.join("other");   query.orderBy(cb. asc (cb.upper((Expression ) (Expression ) otherJoin