ObjectDB Database Search

1-50 of 200 results

jakarta.persistence.criteria.CriteriaBuilder.between(Expression,Y,Y)

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate between ... whether the first argument is between the second and third arguments in value. Parameters: x - value y - value v - expression Returns: between predicate. Since: Jakarta Persistence (JPA) 1.0

jakarta.persistence.criteria.CriteriaBuilder.between(Expression,Expression,Expression)

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate between ... a predicate for testing whether the first argument is between the second and third arguments in value. Parameters: x - expression y - expression v - expression Returns: between predicate. Since: Jakarta Persistence (JPA) 1.0

100% CPU when using multiple BETWEEN

r WHERE (((r.toExtension BETWEEN '2010' AND '2099') OR (r.toExtension BETWEEN '2001' AND '2002')) OR ((r.fromExtension BETWEEN '2010' AND '2099') OR (r.fromExtension BETWEEN '2001' AND '2002'))) ORDER ... (sub second response): SELECT r from RecordingMetaData AS r WHERE (((r.toExtension BETWEEN '2010

Comparison in JPQL and Criteria API

difference between the two sets is the syntax for the equal to ( = vs. == ) and not equal to ( vs ... between any two values that belong to the same group listed above. For example, a double can be compared to a BigInteger instance, but not to a String instance. [NOT] BETWEEN The BETWEEN operator

Database Explorer

makes navigation easier. Because references between database objects are represented as parent-child relationships, you can navigate between objects by expanding nodes, similar to exploring objects in ... between the Shown Fields and Hidden Fields lists. You can change the order of the shown fields by

ObjectDB License Agreement [ver. 2.0.4]

and conditions - do not download, install or use the software. This agreement is between ObjectDB ... , proposal, declaration, warranty, or any communication between the parties. No modification

JPA Query Expressions (JPQL / Criteria)

: = , , = , IS [NOT] NULL , [NOT] BETWEEN Collection operators: [NOT] IN , IS [NOT] EMPTY , [NOT] MEMBER ... , between , isNull , …) Logical expressions ( and , or , not , isTrue )

Retrieving JPA Entities

the field from cascaded retrieval. (ObjectDB currently does not distinguish between these two annotations ... distinguish between these two annotations.) In the preceding example, when an Employee instance

ObjectDB - JPA Object Database for Java

requires slow conversions between graphs of Java objects and flat database table rows. Object Relational ... , including: Avoiding vendor lock in - switching between implementations is easy. Technology

JPA Relationships Annotations

Relationships define associations between entities. They are represented In Java code by attributes (persistent fields or properties) in persistent classes that hold a reference or a collection ... of entity associations: Defines a single-valued association with one-to-one multiplicity between

JPA Criteria API Queries

-based queries are equally powerful and efficient. Therefore, the choice between ... ( equal , notEqual , gt , ge , lt , le , between , isNull , ...) Logical expressions ( and , or , not

Database Management Settings

-building process as a number between 10 and 70. This number indicates a processing rate of 10% to 70

SELECT clause (JPQL / Criteria API)

keyword: SELECT DISTINCT c.currency FROM Country AS c WHERE c.name LIKE 'I%' The only difference between

Detached JPA Entities

objects are useful when an EntityManager is not available or for transferring objects between different

FROM clause (JPQL / Criteria API)

but cannot be one of the following reserved words: ABS, ALL, AND, ANY, AS, ASC, AVG, BETWEEN , BIT

Index Definition

FROM Point p WHERE p.x = 100 SELECT p FROM Point p WHERE p.x BETWEEN 50 AND 80 SELECT p FROM Point p

JPA Query Structure (JPQL / Criteria)

The syntax of the Jakarta Persistence Query Language (JPQL) is similar to SQL. This is a key advantage because SQL is a powerful query language, and many developers are already familiar with it. The main difference between SQL and JPQL is that SQL operates on relational database tables, while JPQL

What is the Java Persistence API (JPA)?

. These implementations are Object Relational Mapping (ORM) tools. The mapping bridges between the data

WHERE clause (JPQL / Criteria API)

between the FROM and SELECT clauses. In practice, if a suitable index is available , the database

Obtaining a JPA Database Connection

. getTransaction (). begin (); A one-to-one relationship exists between an EntityManager instance

Database Schema Evolution

almost insensitive to class hierarchy changes, such as moving fields between class levels or removing

Deleting JPA Entities

=true , specifying CascadeType.REMOVE is redundant. The difference between the two settings

JPA Connections and Transactions

rollback . All database operations between these calls are part of the transaction and are considered

JPA Criteria Query Selection and Results

to be more error-prone (serves as the middle way between index access and using a dedicated  DTO result

JPA Shared (L2) Entity Cache

", CacheRetrieveMode . BYPASS )); The difference between CacheStoreMode.USE and CacheStoreMode.REFRESH

JPA Annotations

associations between entities, such as one-to-one or many-to-many, and specify cascade and fetch

Paths and Types in JPQL and Criteria API

(Country.class)); In the preceding example, the comparison is between the type of the e object

JPA ORM Mapping Annotations

. Specifies the discriminator column used to distinguish between entity types in the SINGLE_TABLE

JPA Components Annotations

) for an entity, mapped superclass, or embeddable class. Enum used with @Access to choose between FIELD

GROUP BY and HAVING clauses

clause acts as a filter between the GROUP BY and SELECT clauses. Only groups that satisfy the HAVING

Database Server

/IP communication between the client and the server, it is usually slower than embedded mode. In

jakarta.persistence.criteria.CriteriaBuilder

expression. Since: Jakarta Persistence (JPA) 1.0 Predicate between ( Expression v , Expression x , Expression y ) Create a predicate for testing whether the first argument is between the second and third arguments in value. Parameters: x - expression y - expression v - expression Returns: between

Using SELECT BETWEEN with LocalDate

I am trying to query all entities whose date is between today and today + X days. The date inside ... Element e WHERE e. date between CURRENT_DATE and :date " , Element. class ) .setParameter( "date ... get the following exception: com.objectdb.o._PersistenceException: Operand type mismatch for operator ' between

Collision Between Different Schema Versions of Entity Classes

Version 2.8.4 fixes a critical bug that in rare cases may cause collision between different schema versions of entity classes, when schemas have changes many times (usually more than 20 times). This bug mainly affects queries on hierarchy of multiple entity classes (i.e. a query on a super class

jakarta.persistence.criteria.JoinType

. Applications which make use of right joins might not be portable between providers or between SQL databases

jakarta.persistence.PersistenceUnitUtil

Jakarta Persistence (JPA) Interface jakarta.persistence.PersistenceUnitUtil Super Interfaces: PersistenceUtil Utility interface between the application and the persistence provider managing the persistence unit. The methods of this interface should only be invoked on entity instances obtained from

jakarta.persistence.PersistenceUtil

Jakarta Persistence (JPA) Interface jakarta.persistence.PersistenceUtil Utility interface between the application and the persistence provider(s). The PersistenceUtil interface instance obtained from the Persistence class is used to determine the load state of an entity or entity attribute

jakarta.persistence.GenerationType

. For a primary key of type Long , Integer , long , or int , the provider selects between TABLE , SEQUENCE

jakarta.persistence.criteria.PluralJoin

, and Double . Support for typecasts between other basic types is not required. Inherited from Expression

jakarta.persistence.criteria.Path

, and String expressions to Integer , Long , Float , and Double . Support for typecasts between other basic

jakarta.persistence.criteria.Predicate

between other basic types is not required. Inherited from Expression Parameters: type - a basic type

jakarta.persistence.criteria.MapJoin

to Integer , Long , Float , and Double . Support for typecasts between other basic types is not required

jakarta.persistence.criteria.ParameterExpression

expressions to Integer , Long , Float , and Double . Support for typecasts between other basic types is not

[ODB1] Chapter 5 - JDO Connections

between these two instances). The currentTransaction() method can be called on any PersistenceManager ... .retry.max", "10"); // Wait 100 milliseconds between every two tries: System.setProperty("com.objectdb ... transaction - in which case an exception is thrown). Usually the only difference between the two modes

Step 4: Create an ObjectDB Data Set

a specified range: SELECT p.x as x, p.y as y FROM Point p WHERE p.x BETWEEN :low AND :high Use copy

[ODB1] Chapter 6 - Persistent Objects

, there is another difference between makePersistent( ... ) and bind( ... ) . The bind( ... ) method is not restricted ... string values between web pages is easier than passing real object ID instances. In this case ... store transactions (which is the default in ObjectDB), there is a strong relationship between

[ODB1] Chapter 8 - ObjectDB Server

are the same in both modes, switching between these two modes can be done very easily by simply changing ... when the communication between the client and the server is over an unsecured network, such as the Internet

[ODB1] Chapter 9 - ObjectDB Explorer

advantage of using the browser window is in navigation among objects. Because every reference between ... fields of the class (in the selected view) using the Left and Right arrow buttons to move fields between

[ODB1] Chapter 7 - JDOQL Queries

on the result collection. There is, however, one important difference between the result collection

[ODB1] Chapter 4 - JDO Metadata

a collection or array should be stored as embedded objects or not. To understand the difference between