ObjectDB Database Search
1-50 of 200 resultsjakarta.persistence.criteria.CriteriaBuilder.or(Predicate...) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate or ... . A disjunction of zero predicates is false. Parameters: restrictions - zero or more restriction predicates Returns: or predicate. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.CriteriaBuilder.or(List) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate or ... . A disjunction of zero predicates is false. Parameters: restrictions - a list of zero or more restriction predicates Returns: or predicate. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.criteria.CriteriaBuilder.or(Expression,Expression) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate or ( Expression x , Expression y ) Create a disjunction of the given boolean expressions. Parameters: x - boolean expression y - boolean expression Returns: or predicate. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.Predicate.BooleanOperator.OR Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.criteria.Predicate.BooleanOperator OR Since: Jakarta Persistence (JPA) 1.0 | |
setting activation code in persistence.xml or env file or system properties Wondering if it's possible to add the activation code either: - in persistence.xml - or in a .env file - or system properties dmoshal David Moshal These options are not supported. However, you can embed the configuration file with the activation code as a resource, e.g. by replacing the objectdb | |
Programatic configuration or configuration file loaded from classpath or file classloader? If one or both are possible, could you please give some examples? Thanks a lot! itsme Martin | |
Privacy Policy shall have the same meaning regardless of whether they appear in singular or in plural. Definitions ... our Service or parts of our Service. Company (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to ObjectDB Software Ltd, 109 Vernon House Friar Lane Unit 632 | |
Apache License, Version 2.0, January 2004 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright ... and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause | |
Which API should I use - JPA or JDO? You can use ObjectDB with either the Java Persistence API (JPA) or the Java Data Objects (JDO) API. Both share similar architecture, design and abilities. When to prefer JPA JPA is more commonly used. Therefore, it might be the first choice for most new applications. You can use JPA as | |
Eclipse Public License - v 1.0"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE ... Contributor: i) changes to the Program, and ii) additions to the Program; where such changes and/ or ... . A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or | |
ObjectDB Website - Terms and Conditions of Use from using or accessing this site. The materials contained in this web site are protected by ... one copy of the materials (information or software) on ObjectDB Software's web site for personal, non ... , and under this license you may not: modify or copy the materials; use the materials for any commercial | |
ObjectDB License Agreement [ver. 2.0.4] Please read carefully this software license agreement. By downloading, installing or using ... and conditions - do not download, install or use the software. This agreement is between ObjectDB ... prevail over any conflicting or additional terms of any oral or written quote, acknowledgement | |
JPA Runtime Tuning & Configuration , @Table ) or set globally at the persistence unit level during bootstrapping . This section describes dynamic options that control runtime behavior and allow you to adjust settings per session, query, or ... ): Defaults passed in a property map to the factory builder or defined in persistence.xml . EntityManager | |
JPA Persistable Types types and serializable types (user-defined or system-defined). Note : Only instances of entity classes ... : Must be a top-level class (that is, not a nested or inner class). Must have a public or protected no-argument constructor. Must not be final and must not have final methods or final instance variables | |
Logical Operators in JPQL and Criteria API the following table: Set 1: JPQL / SQL Set 2: Java / JDO AND && OR || NOT ! JPQL uses SQL notation ... :area Valid operands for the AND operator are TRUE , FALSE , or NULL . The following table shows ... the expression false. If one operand is NULL and the other is TRUE or NULL , the result is NULL | |
JPA Attributes Annotations using the following annotations: Sets a field or property of a basic attribute (e.g., primitives ... (Lazy/Eager) and nullability. Specifies a persistent field or property as an embedded attribute. The embedded state is stored in the same table as the owning entity. Specifies a collection field or | |
Eclipse Distribution License - v 1.0. Redistribution and use in source and binary forms, with or without modification, are permitted provided ... the documentation and/ or other materials provided with the distribution. Neither the name of the Eclipse Foundation, Inc. nor the names of its contributors may be used to endorse or promote products derived from | |
JPA Connections and Transactions a persistence unit name as an argument. As an extension, ObjectDB lets you specify a database URL or path ... string that starts with objectdb: or ends with .odb or .objectdb to be a database URL ... ), you must specify an absolute or relative path to a local database file (for example, "my.odb" ). The objectdb | |
Entity Management Settings settings: The agent attribute (with a value of "true" or "false" ) specifies whether to load ... " - ObjectDB uses reflection for non-enhanced classes with no error or warning. "force" - ObjectDB uses ... references in the persistence context (until commit or flush ), regardless of this setting. The level2 | |
JPA ORM Mapping Annotations these annotations: Specifies the mapped column for a persistent property or field. Specifies that a persistent property or field should be persisted as a large object (BLOB or CLOB). Specifies ... class hierarchy. An enumeration defining the strategies: SINGLE_TABLE , JOINED , or TABLE_PER_CLASS | |
Database Schema Evolution (their schema) are transparent to ObjectDB. This includes adding, removing, or modifying constructors, methods ... ( 0 , false , or null ). Fields in the old schema that do not have matching fields in the new schema ... and either the same type or a convertible type, as explained below. A matching field can also be located in | |
Database Explorer . On Windows, you can also run explorer.exe . On Unix or Linux, you can run explorer.sh ... , either write a query in the Query window or select an element to view (such as an entity class in the Schema window, a bookmark in the Database window, or an object in an open Table or Tree window). You can open | |
JPA Entity Fields either the Java transient modifier (which also affects serialization) or the JPA @Transient ... its methods or code. This state is reflected by its persistent fields, including fields inherited from superclasses. When an entity is stored in the database, each persistent field must contain either null or | |
Database Doctor to the new file. Corrupted database files Database files can be damaged or corrupted for several reasons: Hardware failure (for example, a physical hard drive failure or RAM error). Software failure (for example, a bug in the operating system, Java, or ObjectDB). Copying a database file | |
jakarta.persistence.EntityManager identity that is not ( or no longer) associated with any active persistence context. A removed ... to perform operations that affect the state of the persistence context, or that modify the lifecycle state ... instance by mutating the entity directly, or it may request that the state of a detached instance | |
JPA Lifecycle Events and take no arguments. They can have any name and any access level ( public , protected , package , or ... ). @PostPersist : Invoked after a new entity is stored in the database (during a commit or flush operation ... is updated in the database (during a commit or flush operation). @PreRemove : Invoked when an entity | |
Index Definition, which prevents duplicate values in the indexed field. If you try to commit or flush a transaction ... or a unique index if you specify unique="true" . The default value for unique is false ... files. When an entity is stored in the database, every indexed field must contain either null or a value | |
JPA Core Types environments that do not use JTA. Use this interface to explicitly begin , commit , or roll ... the load state of an entity or attribute without triggering lazy loading. An extended utility interface ... schema management, such as creating, dropping, or truncating schemas. Use this interface | |
Database Management Settings. Moving or copying a database file that was not closed properly without its recovery file might corrupt the database. The element specifies the recovery file settings: The enabled attribute ( "true" or "false" ) specifies whether a recovery file is used. The sync attribute ( "true" or "false | |
Setting and Tuning of JPA Queries . To take effect, you must invoke these methods before running a query with getResultList or ... and on commit or flush . COMMIT - Flushes changes only on an explicit commit or flush . In most JPA ... that EntityManager , or at the individual query level, which overrides the EntityManager setting | |
Detached JPA Entities objects are useful when an EntityManager is not available or for transferring objects between different ... to related entities, mark the reference field with CascadeType . DETACH or CascadeType ... , which can be a single entity or a collection of entities: @Entity class Employee { : @OneToOne ( cascade | |
JPA Class Enhancer the CLASSPATH - path to class or jar file(s), *? wildcards supported include: -cp : path to input user ... classes You can specify class files and JAR files for enhancement explicitly or by using wildcards ... the syntax of import statements (for example, test.X for a single class or test.pc.* for a package | |
JPA Metamodel API() method or the EntityManager 's getMetamodel() method. Both methods are equivalent. For example, given ... a specific type by its Class instance: // Get a managed type (entity, embeddable or mapped super classes ... an ID class when you use multiple ID fields or properties. Finally, the EntityType interface adds | |
Paths and Types in JPQL and Criteria API, a parameter, or another path expression) and uses the dot ( . ) operator to navigate through persistent ... to collections, maps, or values of simple types (such as numbers, booleans, strings, and dates). For a path expression to be valid, the user-defined persistent class must contain a persistent field or property | |
JPA Listeners & Callbacks Annotations during specific entity state transitions. These annotations allow you to define methods within an entity or ... can be further configured with annotations that specify lifecycle event listeners. Specifies one or more callback listener classes for the entity or mapped superclass. These listeners respond to lifecycle events | |
Storing JPA Entities calling the persist method or implicitly through a cascade operation. Explicit persist The following ... the EntityManager , or by commit . Referenced embedded objects The following code stores an Employee instance ... fields is also stored. You can do this either by explicitly persisting every reachable object or by | |
Schema Update. This is a complementary operation to renaming or moving these elements in your IDE during source code ... when you rename or move persistable classes to another package. If you run the application with persistable classes that have been renamed or moved in the IDE without a matching schema configuration, ObjectDB | |
Retrieving JPA Entities the persistence context, JPA constructs a new object and populates it with data from the database or ... through the field. Specifying FetchType . LAZY in either the @OneToOne or @ManyToOne annotation excludes ... or @ManyToMany annotation enables cascaded retrieval for the field. (ObjectDB currently does not | |
JPA Criteria Query Selection and Results and ordering, mirroring the SELECT and ORDER BY clauses in JPQL or SQL. These interfaces allow you to specify ... , such as an entity, an attribute, or a computed expression. Because Selection is a superinterface ... ;the result as an array of objects or as individual values by index, alias string or | |
JPA Optimistic and Pessimistic Locking at transaction commit. ObjectDB checks any database object that is being updated or deleted ... every database object that is being updated or deleted and compares the version number of that object in ... lock or a PESSIMISTIC_READ lock on that database object. For example, consider the following code | |
Strings in JPQL and Criteria Queries: The percent sign ( % ), which matches any sequence of zero or more characters. The underscore ... a path expression), and the right operand is the pattern (usually a parameter or literal). For example ... underscore or percent sign, you must precede it with an escape character and specify that character | |
JPA Queries Jakarta Persistence provides powerful APIs for executing database queries using JPQL strings or ... to ObjectDB). Interface for declaring and handling named or positional query parameters. Use ... ("SELECT ... FROM ... WHERE ..."); or Criteria query objects, as described below. For detailed usage | |
ObjectDB License updates. A site license covers installation of ObjectDB on all computers of one company or ... and laptops of employees in that workplace. Servers that are leased or rented from third party web hosting and/ or cloud hosting companies (including shared web hosting and VPS), if the hosted applications | |
JPA Container Injection Annotations the container to inject EntityManager or EntityManagerFactory proxies directly into application components ... of the persistence context: TRANSACTION (default) or EXTENDED (spanning multiple transactions ... a dependency on an EntityManagerFactory , useful for creating EntityManagers manually or accessing factory | |
Obtaining a JPA Database Connection, you can either define a standard persistence unit or provide the file path of the ObjectDB database directly ... . However, with ObjectDB, any valid database file path (absolute or relative) is also accepted. ObjectDB considers any string that starts with the objectdb: prefix or ends with .odb or .objectdb | |
Query Parameters in JPA , parameters and other query elements are represented by objects (of type ParameterExpression or its superinterface, Parameter ) rather than by names or numbers. For more details, see the Parameters in Criteria ... to specify whether they represent a date, a time, or a combination of date and time, as explained in | |
Deleting JPA Entities or implicitly as a result of a cascade operation. Explicit remove To delete an entity from ... if its argument is not an entity instance or if it is a detached entity. It throws a TransactionRequiredException ... a transaction. Cascading remove Marking a reference field with CascadeType . REMOVE ( or CascadeType | |
JPA Components Annotations can access persistent state directly (field access) or through getters and setters (property access). Use these annotations to configure the access type: Sets the access type (FIELD or PROPERTY) for an entity, mapped superclass, or embeddable class. Enum used with @Access to choose between FIELD | |
GROUP BY and HAVING clauses. When a query includes a GROUP BY clause, the database objects ( or tuples) that result from the FROM clause ... ) that are performed on all the objects or object tuples in the group. Aggregate calculations ... of aggregate query that does not have a GROUP BY clause. In these queries, all objects or tuples | |
JPA Exceptions PersistenceException to handle runtime failures. This structure enables applications to catch specific errors or ... without an active transaction. Thrown when the transaction is marked for rollback only or the commit fails ... . This commonly occurs during EntityManager.refresh or EntityManager.getReference calls. Concurrency |