 14 | will affect the way strings are sorted in queries (with ORDER BY). Currently strings are always ordered by Unicode order, and a workaround that enables controlling the order is to use normalizing, as discussed ... , DMS and other systems requires correct collation when using order by clause. +1 for this ... lwalkowski dmarko Arne |
14 | definition or the ORDER BY clause, so the sort uses the correct collation per defined locale. Thank ... (we are Czech company). How the sort order works for international (for us 'czech') letters? Does the ordering respects the national requirements? Thank you for clarification ... ObjectDB uses |
14 | classes) are represented in JPQL by the following types of expressions: Variables - FROM ... and functions (e.g. for strings and for numbers), they can be compared by all six comparison operators, and they can be used in ordering. Navigation through Path Expressions A path expression always starts |
14 | to start by running a live sample application in your IDE, you should be able to follow this tutorial |
13 | an entity object that is already managed by the EntityManager returns the existing instance from ... by the EntityManagerFactory and shared by all its EntityManager objects. the broader scope ... is wider, since they exist per database and are shared by all the EntityManagerFactory and EntityManager |
13 | at the WHERE clause level by using a type expression. For example, in the following query, c iterates ... , and the same query can also be written as follows:
SELECT c FROM Country c
By default, the name ... name). The default name can be overridden by specifying another name explicitly in the @Entity's |
13 | three groups. SELECT and ORDER BY elements (including tuples): FROM clause elements (representing range ... Queries are represented in JPA by the Query and TypedQuery interfaces: The JPA Query API section ... only at runtime (e.g. depending on which fields are filled by a user in a form) can be done by |
13 | (using an ORDER BY clause) and even group results (using GROUP BY and HAVING clauses). JPQL ... a managed entity) by the persist method. The new Point objects are physically stored in the database ... objects in the database by using a simple query: Query q1 = em.createQuery("SELECT COUNT(p) FROM Point |
13 | (using an ORDER BY clause) and even group results (using GROUP BY and HAVING clauses). JPQL ... a managed entity) by the persist method. The new Point objects are physically stored in the database ... objects in the database by using a simple query: Query q1 = em.createQuery("SELECT COUNT(p) FROM Point |
12 | these details to connect to the master server in order to listen to updates. The updates are automatically ... can manage different types of databases, including master databases, slave database (by using ... The configuration above demonstrates a situation in which the master database is managed by a server |