ObjectDB Database Search

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.ListJoin ListJoin on (    Predicate... restrictions ) Modify the join to restrict the result according to the specified ... : restrictions - zero or more restriction predicates Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate and (    List restrictions ) Create a conjunction of the given restriction predicates. A conjunction of zero predicates is true. Parameters: restrictions - a list of zero or more restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate or (    Predicate... restrictions ) Create a disjunction of the given restriction predicates. A disjunction of zero predicates is false. Parameters: restrictions - zero or more restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate or (    List restrictions ) Create a disjunction of the given restriction predicates. A disjunction of zero predicates is false. Parameters: restrictions - a list of zero or more restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate and (    Predicate... restrictions ) Create a conjunction of the given restriction predicates. A conjunction of zero predicates is true. Parameters: restrictions - zero or more restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate not (    Expression restriction ) Create a negation of the given restriction . Parameters: restriction - restriction expression Returns: not predicate. Since: Jakarta Persistence (JPA) 1.0

where (    Expression restriction ) Modify the update query to restrict the target of the update according to the specified boolean expression. Replaces the previously added restriction (s), if any. Parameters: restriction - a simple or compound boolean expression Returns: the modified update query. Since: Jakarta Persistence (JPA) 1.0

where (    Expression restriction ) Modify the DELETE query to restrict the target of the deletion according to the specified boolean expression. Replaces the previously added restriction (s), if any. Parameters: restriction - a simple or compound boolean expression Returns: the modified delete query. Since: Jakarta Persistence (JPA) 1.0

having (    Expression restriction ) Specify a restriction over the groups of the query. Replaces the previous having restriction (s), if any. This method only overrides the return type of the corresponding AbstractQuery method. Parameters: restriction - a simple or compound boolean expression

where (    Expression restriction ) Modify the query to restrict the query result according to the specified boolean expression. Replaces the previously added restriction (s), if any. This method only overrides the return type of the corresponding AbstractQuery method. Parameters: restriction

the predicate that corresponds to the where clause restriction (s), or null if no restrictions

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CollectionJoin CollectionJoin on (    Expression restriction ) Modify the join to restrict the result according ... . Parameters: restriction - a simple or compound boolean expression Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.SetJoin SetJoin on (    Expression restriction ) Modify the join to restrict the result according to the specified ON condition and return the join object. Replaces the previous ON condition, if any. Parameters: restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.ListJoin ListJoin on (    Expression restriction ) Modify the join to restrict the result according to the specified ... : restriction - a simple or compound boolean expression Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Join Join on (    Expression restriction ) Modify the join to restrict the result according to the specified ON condition and return the join object. Replaces the previous ON condition, if any. Parameters: restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.MapJoin MapJoin on (    Expression restriction ) Modify the join to restrict the result according to the specified ON condition and return the join object. Replaces the previous ON condition, if any. Parameters: restriction

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.AbstractQuery Predicate getGroupRestriction() Return the predicate that corresponds to the restriction (s) over the grouping items, or null if no restrictions have been specified. Returns: having clause predicate. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CommonAbstractCriteria Predicate getRestriction() Return the predicate that corresponds to the where clause restriction (s), or null if no restrictions have been specified. Returns: where clause predicate. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Join Predicate getOn() Return the predicate that corresponds to the ON restriction (s) on the join, or null if no ON condition has been specified. Returns: the ON restriction predicate. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.Predicate Super Interfaces: Expression , Selection , TupleElement The type of a simple or compound predicate: a conjunction or disjunction of restrictions . A simple predicate is considered to be a conjunction with a single conjunct

." This is a NetBeans restriction , not a JPA restriction . "An entity or IdClass class should implement the java.io.Serializable interface." This is also a NetBeans restriction , not a JPA restriction . "There is no ID ... may not be final." This is a JPA restriction . ObjectDB supports also final entity classes . "The project

and regards Benjamin Klink bklink Benjamin Klink JPQL restricts ORDER BY expressions to expressions ... .lastname = ‘Smith’ AND c.firstname = ‘John’ ORDER BY p.price ObjectDB is less restrictive , and will except the query above. However, in DISTINCT and GROUP BY queries it must follow these restrictions

the evaluation license restriction message again at compile time (which was I was seeing before putting ... about the 10 class restriction . In one case it happened after Linode did 'scheduled' maintenance ... about restrictions ? BTW: this happened with objectdb 2.3.7_09 I'm upgrading to 2.4.0_04 today fyi

(including commercially) under a restriction of maximum 10 entity classes and one million entity ... to remove this restrictions . Anyway, you need a license key to remove this restriction . support Joined

page : ObjectDB can also be used freely (including commercially) under a restriction of maximum 10 ... companies are required to purchase a license to remove this restrictions . Anyway, you need a license key to remove this restriction . support Support thanks alot your replay makes every thing clear now eng.ahmed ahmed

and set the new database in production. It just didn't want to respect the restrictions . I had to delete ... project. So, the bottom line is that ODB seems to do not respect the restriction when a fresh DB

, but also some restrictions . ObjectDB, however, does not enforce these restrictions so mapped superclasses

1. In general, are there any restrictions of the use of @Embedded objects in collections, compared to @Entity ? 2. If you have a large nested collection of @Embedded objects, and you remove ... , Integer ) with no particular restrictions (except the ordinary limitations of embedded objects ). Use

like to know more about this. It looks very useful. 1. Are there any restrictions on the depth ... Ben Schreiber Regarding the new syntax - there is no restriction on the depth of nested collections

edition has a restriction of  maximum 10 entity classes and one million entity objects ... from a free license removes the restrictions with no need to upgrade the database or the code

$. Also we can't restrict ourselves for 10 entities :).   So I wonder if it's possible to gain some kind of less restrictive ObjectDB license for Open Source project.  Thank you for your answer.  

ObjectDB database files without the free edition restrictions . Any ObjectDB 2.x database file

. Shane1234 Shane Murray It is a restriction of the free edition. Please see this license page . support Support

My activation code works fine on my computer Ubuntu but fails on the same machine if I boot into Windows 8.  Is the activation code restricted to an operating system?  Would I lose it's use if I upgraded Ubuntu at some point?  sjzlondon Steve Zara You should be able to use

Hello! How does ObjectDB determine the machine ID? Yesterday I activated our license on my development laptop and today I tried to persist more than 1M objects. ObjectDB told me that it cant't do that because of the evaluation restrictions . Now I activated it again on the same machine and got

Hi, We have a ObjectDB instalation and licence for one server on a virtual machine within ESXi, we would like to migrate it to Physical server, is there any restrictions in moving or when reinstaling a server with ObjectDB instalation. Thank you. peric.emil Emil Perić A Server license is non

, and apparently Eclipse class loader is not supported. In addition, please notice this restriction

. The rules for primary keys are more restrictive , as explained on the primary key page. Probably

am aware of that sorry ;) What I was trying to say.. how can I restrict the DISTINCT to the first

Chris Powell I should add that this is on the restricted version! Also, I can see entities one-by

by the OS in the large available RAM. Virtualization can restrict the available resources, i.e

restarting the server and waiting to some other threads to complete. This waiting was restricted now

(probably with a restriction of one collection). support Support Hello, yes, one collection

so we can avoid the single-process restriction though still have multiple processes to avoid a SPOF? Yes, the OEM

I was about to post (here, since the provided url is restricted ), I noticed there was a new release

? Indeed it seems restrictive . We plan to switch to a new automatic activation system, so ObjectDB would be able

an attempt to remove this restriction , which you may try. support Support

Why does the below code not enforce unique restrictions ?   Person @Entity @Unique(members = {"name", "surname"}) public class Person implements Serializable {     @Id     @GeneratedValue     private Integer id;     private String

Restricted waiting time on closing a database on a server to 2 seconds(see issue #2686 ).

contains only a restricted schema, here we have the only one not enhanced entity 'TCVector' (is not