ObjectDB Database Search
51-100 of 200 resultsfind repeated records by JPQL in #1 contains GROUP BY / HAVING. The outer query in #1 contains the IN operator. The query in #3 ... get the point since in #3 there is no GROUP BY / HAVING. support Support ... (select id from TTT s group id having count(id)1) I dont know how to do this using JPQL, but I use | |
Problem with distinct select, order by and equivalent alias/attribute path, and will except the query above. However, in DISTINCT and GROUP BY queries it must follow these restrictions ... when ordering the results of some projection when the order by expression is different (though logically ... ; + "order by s_location.id asc";   | |
Help with JPA2 Criteria and conditional operator grouping; ))); System.out.println("Query: " + c); But I can can never get the grouping to occur ... persistence.xml shows the grouping happening. I've had to dumb down the domain model enough to convey ... . support Support That fixed the conditional grouping issue. Thanks. There is a new problem now however, I'll create a new post Willks William | |
ObjectDB Roles and Groups Hello, How can I incorporate roles/ group in ObjectDB config file? I see no support for this. For example, I would like to place several users under a given group or role, but I see no way of doing this as no such element is present in the config file. Is it possible to have this? st.clair | |
Entity can be found by find() but not by query and sometimes we don't get the entity by query. Have you an idea what happens here? btc_es BTC EmbeddedSystems | |
Shared (L2) Entity Cache an entity object that is already managed by the EntityManager returns the existing instance from ... objects, which is managed by the EntityManagerFactory and shared by all its EntityManager objects ... . The scope of these server side caches is wider, since they exist per database and are shared by | |
Database Connection using JPA A connection to a database is represented by an EntityManager instance, which also provides ... . An EntityManagerFactory is constructed for a specific database, and by managing resources efficiently (e.g ... the content of a database require active transactions. Transactions are managed by an EntityTransaction | |
JPA Lifecycle Events and are invoked automatically by JPA when these events occur. Internal Callback Methods Internal callback ... - after an entity has been retrieved from the database. @PreUpdate - when an entity is identified as modified by ... for the same event. However, the same method may be used for multiple callback events by marking | |
Working with JPA Entity Objects are provided in the Storing Entities section. Entity objects retrieved from the database by ... is detected by the owning EntityManager and the update is propagated to the database on transaction ... (except retrieval by refresh , which always requires accessing the database). The main role of the persistence | |
InterfaceRef jakarta.persistence.criteria.AbstractQuery a list of the grouping expressions. Returns empty list if no grouping expressions have been specified. Modifications to the list do not affect the query. Return: the list of grouping expressions ... ) over the grouping items, or null if no restrictions have been specified. Return: having clause | |
InterfaceRef jakarta.persistence.criteria.Subquery of the grouping expressions. Returns empty list if no grouping expressions have been specified. Modifications to the list do not affect the query. Return: the list of grouping expressions Inherited from ... to the restriction(s) over the grouping items, or null if no restrictions have been specified. Return | |
InterfaceRef jakarta.persistence.criteria.CriteriaQuery: AbstractQuery Since: JPA 2.0 List getGroupList () Return a list of the grouping expressions. Returns empty list if no grouping expressions have been specified. Modifications to the list do not affect the query. Return: the list of grouping expressions Inherited from: AbstractQuery Since: JPA 2.0 Predicate | |
SELECT clause (JPQL / Criteria API), the following query returns Country objects that become managed by the EntityManager em : TypedQuery query ... in the results directly, but their content can be added to the SELECT clause by using a bound JOIN ... that are retrieved directly by a result path expression are not associated with an EntityManager and changes | |
Literals in JPQL and Criteria Queries literals (e.g. 077 , 077L ), a feature that is not currently supported by all JPA implementations. String ... single quotes (e.g. 'Adam' , '' ) and a single quote character in a string is represented by ... can be used (e.g. "Adam\'s" , "abcd\n1234" ) but this is not supported by all the JPA implementations | |
ObjectDB Website - Terms and Conditions of Use 1. Terms By accessing and using this web site, you agree to be bound by these web site Terms ... from using or accessing this site. The materials contained in this web site are protected by ... of these restrictions and may be terminated by ObjectDB Software at any time. Upon terminating your viewing | |
ObjectDB License Agreement [ver. 2.0.5] Please read carefully this software license agreement. By downloading, installing or using ... of this agreement will be binding, unless in writing and signed by an authorized representative of each party. 1 ... by this agreement. 3. The free edition of the Software includes restrictions on the number of classes | |
JPA Exceptions JPA exceptions are represented by a hierarchy of unchecked exceptions: java.lang.Object java.lang ... are represented directly by the PersistenceException class. Some specific errors are represented by ... transaction is represented by : Database update failures that require transaction rollback are represented by | |
Database Transaction Replayer. Recording is enabled by default and can be disabled in the configuration . The ObjectDB Replayer tool ... is useful for two different purposes: It enables recovery from a database failure by replaying the recorded operations. It enables reproducing problems during debugging by repeating a failure. Backup | |
Setting and Tuning of JPA Queries in Query and TypedQuery support method chaining ( by returning the query object ... to be visible to the query. Flush policy in JPA is represented by the FlushModeType enum, which has two values ... the default is COMMIT (which is more efficient). The default mode can be changed by the application | |
JPA Metamodel API Metamodel API is Metamodel . It can be obtained either by the EntityManagerFactory 's getMetamodel method or by the EntityManager 's getMetamodel method (both methods are equivalent). For example, given an EntityManager , em , a Metamodel instance can be obtained by : Metamodel metamodel = em | |
BIRT/ODA ObjectDB Driver language. For step by step instructions on using BIRT with ObjectDB see the Report Generation ... Developers extension. To install it: Open the [Install] dialog box by selecting Help Install New Software ... and press ENTER. Select the ObjectDB Birt/ODA feature. Complete the installation by clicking Next twice | |
Database Server, if an ObjectDB database is accessed directly only by a web application, it should be embedded in ... configuration is loaded automatically as explained in chapter 6 . This can be overridden by specifying ... the Server Configuration , but can be overridden by an explicit command line option: $ java com.objectdb | |
Support for roles/groups in ObjectDB ObjectDB should incorporate roles/ group in ObjectDB config file? I see no support for this. I would like to place several users under a given group or role, but I see no way of doing this as ... , there could be a role/ group element which would categorise the user further. This would help in authentication. Thanks st.clair.clarke St Clair Clarke | |
Database Doctor of a corrupted ObjectDB database file Repairs a corrupted ObjectDB database file by creating a new ... - if the recovery file is disabled. Using the database file simultaneously by two instances ... . Modifying the database file externally not through ObjectDB (e.g. by malicious software such as | |
Entity Management Settings are handled. ObjectDB can manage non enhanced classes by using reflection at the cost of performance ... entities are always held by strong references in the persistence context (until commit or flush ... that is managed by the EntityManagerFactory and shared by all its EntityManager instances. The level 2 cache | |
Online Backup An ObjectDB database can be backed up by simply copying or archiving the database file while the database is offline (i.e. when it is not open in an ObjectDB server and not in use by any application ... . Starting Online Backup The online backup can be started by executing a special query on an EntityManager | |
General Settings and Logging a limit size that is specified by the threshold attribute. The mb and kb suffixes represent megabytes ... has to be specified for ObjectDB to avoid using sockets that are expired by the firewall. The element ObjectDB manages a list of the recently accessed database URLs for use by the Explorer | |
InterfaceRef jakarta.persistence.EntityManagerFactory the set of all classes that are related or grouped by the application, and which must be colocated in ... , then they must belong to the same persistence unit. A persistence unit may be defined by a persistence.xml file ... programmatically via the EntityTransaction interface. An EntityManagerFactory with a lifecycle managed by | |
Mapped by fields are not initialized by JOIN FETCH in queries As demonstrated in this forum thread , a mapped by collection field with lazy fetch mode is not initialized in results of a query that uses JOIN FETCH on that collection field (when enhancement is used). support Support Build 2.4.1_06 fixes this issue (fields are now initialized | |
AnnotationRef jakarta.persistence.MapKeyJoinColumns composite map keys that reference entities. The MapKeyJoinColumns annotation groups ... and the referencedColumnName elements must be specified in each of the grouped MapKeyJoinColumn annotations ... annotation element is specified in either location, a default foreign key strategy is selected by | |
Server Configuration is affected also by other elements in the configuration file, particularly the and the configuration elements ... . If another port is specified it also has to be specified by clients in the URL connection string ... specifies the maximum number of simultaneous connections that are accepted by the server. A request | |
Database Replication and Clustering ObjectDB server can manage different types of databases, including master databases, slave database ( by ... The configuration above demonstrates a situation in which the master database is managed by a server on localhost:6000 and the slave database is managed by a server on localhost:6001 . In this case | |
Logical Operators in JPQL and Criteria API || NOT ! JPQL follows the SQL notation, while Java uses its own notation (which is also in use by JDOQL ... expressions are represented in criteria queries by Expression and descendant interfaces. For example, a boolean path (a field or a property) is represented by Path : Path isInUN = country | |
Index Definition Querying without indexes requires iteration over entity objects in the database one by ... on more than one persistent field. It is defined by specifying multiple fields in the members attribute ... a collection, so multiple values will be maintained by the index for every entity. Multi part paths in | |
Numbers in JPQL and Criteria Queries The following arithmetic operators are supported by JPA: 2 unary operators: + (plus) and - (minus). 4 ... of the same type. The MOD Function The MOD function calculates the remainder of the division of one number by another, similar to the modulo operator ( % ) in Java (which is also supported by ObjectDB as | |
JPA Named Queries named queries instead of dynamic queries may improve code organization by separating the JPQL ... carefully to avoid collision (e.g. by using the unique entity name as a prefix). It makes sense to add ... at Runtime Named queries are represented at runtime by the same Query and TypedQuery interfaces | |
JPA Query API Queries are represented in JPA 2 by two interfaces - the old Query interface ... with an EntityManager (represented by em in the following code snippets), which serves as a factory ... which retrieves all the Country objects in the database is represented by both q1 and q2 . When building | |
Deleting JPA Entity Objects Existing entity objects can be deleted from the database either explicitly by invoking the remove ... committed the object is not deleted. An IllegalArgumentException is thrown by remove if the argument ... should be cascaded automatically to entity objects that are referenced by that field (multiple entity objects | |
Chapter 6 - Configuration: This page explains how ObjectDB configuration works in general. The Configuration Path By default ... explicitly by setting the "objectdb.home" system property: System.setProperty("objectdb.home", "/odb ... : $ java "-Dobjectdb.home=/odb" ... The Configuration File As noted above, by default | |
Updating JPA Entity Objects by fields that are marked with CascadeType . PERSIST or CascadeType . ALL are also persisted ... yet are also persisted. Automatic Change Tracking As shown above, an update is achieved by modifying a managed ... demonstrated above, array changes are not detected automatically ( by default) but it is possible | |
Chapter 1 - Quick Tour This chapter demonstrates basic ObjectDB and JPA concepts by introducing a simple example program ... that contains points in the plane. Each point is represented by an object with two int fields, x and y, that hold the point's x and y coordinates. The program demonstrates CRUD database operations by | |
Step 3: Define an EJB Session Bean Operations on the database will be performed by an instance of a session bean (EJB) class that we will define in this step: Open the [New Session Bean] dialog box by right clicking the guest package ... getAllGuests() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class | |
Step 3: Define an EJB Session Bean Operations on the database will be performed by an instance of a session bean (EJB) class that we will define in this step: Open the [New Java Class] dialog box by right clicking the guest package ... Guest g ORDER BY g.id", Guest.class); return query.getResultList(); } } The GuestDao session bean (EJB | |
Step 1: Install BIRT and ObjectDB Driver We start by installing the BIRT development environment and the ObjectDB data source driver ... IDE for Java EE Developers. Update your existing Eclipse IDE for Java EE Developers environment by ... an existing Eclipse IDE for Java EE Developers environment: Open the [Install] dialog box by | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right ... () { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return | |
Step 3: Define a Spring DAO Component Operations on the database will be performed by an instance of a Data Access Object (DAO) that we will define in this step as a Spring MVC component: Open the [New Java Class] dialog box by right ... getAllGuests() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return | |
Step 3: Add a Context Listener Class The Guest entity objects will be stored in an ObjectDB database, which will be represented by ... created if not existing yet) when the web application starts, by instantiating an EntityManagerFactory . The database will be closed when the web application stops (or when the web server shuts down), by | |
Step 6: Design a BIRT Report Table In this final step we will add a simple table to the report: Open the [Insert Table] dialog box by ... ) layout. Set the column number to 2 , number of details to 1 , select the data set (e.g. Points by X ) in the third field and click OK . Fill the table with data by dragging the x and y columns from | |
Step 1: Create a Web Project We start by creating a new Eclipse Dynamic Web Project: Open the [New Project] dialog box, e.g. by ... as a new server by clicking the New Runtime... button . Follow the instructions and specify the path ... web project. Now, add ObjectDB support to the new Eclipse Project - by dragging the objectdb | |
Step 3: Add a Context Listener Class The Guest entity objects will be stored in an ObjectDB database, which will be represented by ... created if not existing yet) when the web application starts, by instantiating ... down), by closing the EntityManagerFactory . To register a ServletContextListener : Open the [New |