ObjectDB Database Search
151-200 of 200 resultsobjectdb explorer in ver 2.2 and 1.0 You are right - some important features of ObjectDB 1 .0 Explorer are not implemented yet in ObjectDB 2.2 ... to the Explorer, including support of running queries and editing databases. Additional features will be added to the Explorer in future versions. Support of ObjectDB 1 .x is now limited, so new application | |
ObjectDB version 2.1 has been released ObjectDB 2. 1 has been released and it includes important additions and fixes: Added Online Backup utility ( issue #16 ). Added Master-Slave Replication / Clustering (issue #17 ). Added a PDF ... ( issue #142 ). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in | |
GlassFish 3.1.2.2/JBoss 7.1.1). May be you have some ideas? When we just try JBoss 7. 1 . 1 nothing works at all. Where I can get a real ... . webel Dr Darren Kelly As discussed in a previous forum thread - JBoss 7. 1 . 1 is expected to be supported ... there are also issues with GlassFish 3. 1 .2 (GlassFish 3. 1 . 1 may work better with ObjectDB | |
Closed EntityManagerFactory after upgrading glassfish 3.1.1 to 3.1.2 Hi. I have faced a very serious issue. After upgrading the GlassFish server from 3. 1 . 1 to 3. 1 .2 ... ) at com.n2nconnect.mm.jsf.controller.ProjFeedController$ 1 .createPageDataModel(ProjFeedController.java:60 ... more It seems that there is something wrong with persistent context. it seems that glassfish 3. 1 .2 behaves differently. I | |
Criteria query error: Unexpected query token.arquillian.spi.ArquillianProxyException: com.objectdb.o._PersistenceException : Unexpected query token ... ", initialValue = 1 , allocationSize = 50) // @GeneratedValue(strategy = GenerationType.SEQUENCE ... to see? Or is Criteria a W.I.P? Cheers Willks William It seems that the query is invalid | |
NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1 + Jboss 7. 1 . 1 @Entity public class Person extends AbstractObject { private static final long ... ); The exception: java.lang.NoSuchFieldError: __odbTracker test.City.__odbSet_name(City.java: 1 ) test.City.setName ... .interceptors.UserInterceptorFactory$ 1 .processInvocation(UserInterceptorFactory.java:36) org.jboss | |
[ObjectDB 2.4.1] Unexpected exception (Error 990) Hi, getting this unexpected exception, would welcome advice: [ObjectDB 2.4. 1 ] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Client VM 1 .6.0_29 (on Windows 7 6. 1 ... .runners.model.FrameworkMethod$ 1 .runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners | |
JPQL Update & Delete (JPA 1.0) JPQL (Java Persistence Query Language) supports updating and deleting database objects by queries . Currently ObjectDB supports only JPQL SELECT (retrieval) queries . Delete queries are supported for JDOQL (JDO Query Language). support Support spring-data-jpa uses delete queries to implement | |
jakarta.persistence.criteria.Expression: - the type of the expression Super Interfaces: Selection , TupleElement Type for query expressions. Since: Jakarta Persistence (JPA) 2.0 The JPA Query Expressions (JPQL / Criteria) article explains ... Persistence (JPA) 1 .0 Expression as ( Class type ) Perform a typecast upon the expression, returning a new | |
JPA Extended API Reference Guide, query facilities, metamodel details, configuration options, annotations, and exception information ... the fundamental classes and interfaces for entity management and persistence operations. Covers the query API, criteria queries , and JPQL for data retrieval and manipulation. Describes the metamodel and graph APIs | |
What are the main benefits of using ObjectDB? processes JPQL (JPA Query Language) and JDOQL (JDO Query Language) queries directly, where ORM tools first convert these queries to SQL and then transition the SQL to the DBMS for execution through a JDBC | |
JPQL Subqueries (JPA 1.0) The JPQL (Java Persistence Query Language) supports defining subqueries, which are nested queries that are embedded in other queries . Subqueries are currently not supported by ObjectDB, and as a workaround, you can use a sequence of two or more queries , where the results of one query serves as a parameter in the next queries . support Support | |
jakarta.persistence.criteria.Predicate Persistence (JPA) 1 .0 Expression as ( Class type ) Perform a typecast upon the expression, returning ... . See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast ... (JPA) 1 .0 List getCompoundSelectionItems () Return the selection items composing a compound selection | |
Typo in ObjectDB 1.0 Manual Support Knowledge Base ObjectDB 1 .0 Manual Chapter 7 "JDOQL Queries " Section 7.2 " Query Filter Syntax" Subsection "Fields" Second to last sentence Remove "not" from that sentence. "An attempt ... there is also a quoting issue on the query .setFilter() line in section 7.5 sub section "Nested Bound Variables".   | |
JDOQL Subqueries (JDO 2.1) Subqueries (nested queries ) have been added to JDOQL (JDO Query Language) in JDO 2. 1 . This is the main feature of JDO 2.0-2. 1 -2.2 that is not implemented yet in ObjectDB 2. support Support | |
ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6. 1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries . Fixed a bug in queries on deleted objects before commit / flush. | |
[ObjectDB 2.5.1_05] Unexpected exception (Error 990) I have this error in log. The query can't return result. Thanks for help. LOG: [ObjectDB 2.5. 1 _05] Unexpected exception (Error 990) Generated by Java HotSpot(TM) Server VM 1 .7.0_55 (on Windows Server 2008 R2 6. 1 ). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb | |
ObjectDB 2.8.1 Improved query plan evaluation (including for selecting composite indexes). Fixed new statistics collection for queries . Fixed a bug in LEFT OUTER JOIN queries ( issue #2438 ). | |
ObjectDB 2.5.1 (inverse) relationships. Fixed a bug in using IN expression in criteria queries . Fixed processing an IN(:param) expression in JPQL queries . | |
jakarta.persistence.Tuple correspond to an element in the query result tuple. Since: Jakarta Persistence (JPA) 1 .0 X get ( int ... the elements of a query result tuple. See Also: TupleElement Since: Jakarta Persistence (JPA) 2.0 Public ... - if tuple element does not correspond to an element in the query result tuple. Since: Jakarta | |
ObjectDB 2.3.1 a ClassCastException in using a composite index in queries ( issue #521 ). Fixed handling derived Id | |
ObjectDB 2.1.0 to NonTransactionalWrite enabled ( issue #142 ). Fixed a bug in distinct queries (duplicates due to bad | |
jakarta.persistence.criteria.CriteriaBuilder.SimpleCase which they are specified. Since: Jakarta Persistence (JPA) 1 .0 Public Instance Methods Selection alias ... : selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform ... expression of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast | |
jakarta.persistence.criteria.Path (JPA) 1 .0 Expression as ( Class type ) Perform a typecast upon the expression, returning a new ... ) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression ... to the referenced attribute. Since: Jakarta Persistence (JPA) 1 .0 Expression get ( PluralAttribute | |
jakarta.persistence.criteria.CriteriaQuery.multiselect(Selection...) in the query result. Replaces the previously specified selection(s), if any. The type of the result of the query execution depends on the specification of the type of the criteria query object ... : If the type of the criteria query is CriteriaQuery (i.e., a criteria query object created by | |
jakarta.persistence.criteria.CriteriaQuery.multiselect(List) the query result. Replaces the previously specified selection(s), if any. The type of the result of the query execution depends on the specification of the type of the criteria query object created as ... follows: If the type of the criteria query is CriteriaQuery (i.e., a criteria query object created | |
jakarta.persistence.SqlResultSetMapping query or stored procedure. Example: Query q = em.createNativeQuery( "SELECT o.id AS order_id, " + "o ... = "item_name") }) See Also: Query StoredProcedureQuery NamedNativeQuery NamedStoredProcedureQuery Since: Jakarta Persistence (JPA) 1 .0 Annotation Elements String name The name given to the result set | |
jakarta.persistence.criteria.CriteriaBuilder.Case which they are specified. Since: Jakarta Persistence (JPA) 1 .0 Public Instance Methods Selection alias ( String ... : selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform a typecast ... of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ( Class | |
jakarta.persistence.EntityResult the SELECT clause of a SQL query to an entity result. If this annotation is used, the SQL statement ... . Example: Query q = em.createNativeQuery( "SELECT o.id, o.quantity, o.item, " + "i.id, i.name, i ... NamedNativeQuery Since: Jakarta Persistence (JPA) 1 .0 Annotation Elements Class entityClass | |
JPA Metamodel and Graphs, and their attributes to build dynamic queries and validate persistence structures. The Metamodel Access ... and further explanation, refer to the JPA Metamodel API section in the ObjectDB manual. Criteria query ... objects that can be bound to a Path in a Criteria query , mainly to define FROM variables | |
Posting Sample Code; em.getTransaction().commit(); Query query = em.createQuery("SELECT e FROM MyEntity e"); List resultList = query | |
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct), the inability to robustly query relationship fields in a web application renders the ObjectDB system seemingly useless. objectdb-2.2.5_10 NetbeansIDE6.9. 1 Glassfish3.01 client-server mode. odb file ... showing the query result in indexTest.xhtml. The problems is illustrated by running the attached JavaEE | |
jakarta.persistence.criteria.CriteriaBuilder.Coalesce otherwise. Since: Jakarta Persistence (JPA) 1 .0 Public Instance Methods Selection alias ( String ... : selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression as ( Class type ) Perform a typecast ... of the given type. See Also: .cast(Class) Since: Jakarta Persistence (JPA) 1 .0 Expression cast ( Class | |
jakarta.persistence.ColumnResult ConstructorResult annotation to map a column of the SELECT list of a SQL query . The name element references ... can be included in the query result by specifying this annotation in the metadata. Example: Query q = em ... NamedNativeQuery ConstructorResult Since: Jakarta Persistence (JPA) 1 .0 Annotation Elements String | |
jakarta.persistence.TypedQueryReference.0 String getName () The name of the query . Since: Jakarta Persistence (JPA) 1 .0 Class getResultType () The result type of the query . Since: Jakarta Persistence (JPA) 1 .0 ... : - an upper bound on the result type of the query A reference to a named query declared via the NamedQuery | |
jakarta.persistence.NonUniqueResultException Thrown by the persistence provider when Query .getSingleResult or TypedQuery.getSingleResult is executed and there is more than one result from the query . This exception does not cause the current transaction, if one is active, to be marked for rollback. See Also: Query .getSingleResult() TypedQuery | |
jakarta.persistence.NamedQueries mapped superclass. See Also: NamedQuery Since: Jakarta Persistence (JPA) 1 .0 The JPA Named Queries ... : Annotation Target: Type Declares multiple named Jakarta Persistence query language queries . Query ... of NamedQuery annotations. Since: Jakarta Persistence (JPA) 1 .0 Additional JDK methods inherited | |
Unexpected Query Token / Casting in Query Hi! Please find the attached database. Doing a simple query with casting SELECT COUNT(DISTINCT $ 1 ) FROM com.quasado.foundation.contact.individual.IndividualContact $ 1 WHERE UPPER(((com.quasado.foundation.warehouse.api.model.account.contact.IndividualContactDebitorAccountFragment) $ 1 | |
jakarta.persistence.LockModeType refresh() ), or to Query .setLockMode or TypedQuery.setLockMode . Optimistic locks are specified using ... attempting to update the entity data. A lock with LockModeType.PESSIMISTIC_READ can be used to query ... with LockModeType.PESSIMISTIC_WRITE can be used when querying data and there is a high likelihood of deadlock or | |
jakarta.persistence.criteria.Fetch: the resulting fetch join. Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( SingularAttribute ... Returns: the resulting fetch join. Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( PluralAttribute ... . Since: Jakarta Persistence (JPA) 1 .0 Fetch fetch ( PluralAttribute attribute , JoinType jt ) Create a fetch | |
jakarta.persistence.criteria.Selection that is to be returned in a query result. Since: Jakarta Persistence (JPA) 2.0 The SELECT clause (JPQL ... . Since: Jakarta Persistence (JPA) 1 .0 String getAlias () Return the alias assigned to the tuple element or ... Persistence (JPA) 1 .0 List getCompoundSelectionItems () Return the selection items composing a compound | |
queries under 2.7.6_4 significantly slower than under 2.7.6 200 seconds and reports in query plan: Query plan 1 /2 description ... -Georg Zwicker forgot, query plan for 2.7.6: Query Plan Description ====================== Step 1 ... . To see how it works you can try the following 2 queries in the Explorer (with build 2.7.6_06) : Query 1 | |
JPA Fetch Plan Graphs Jakarta Persistence (JPA) Entity Graphs optimize query performance by specifying which attributes should be loaded eagerly. Graph definitions Use the following interfaces to define ... as a template for a query or find operation, allowing you to override the default fetch strategies | |
JPA Connections and Transactions the EntityManager . An EntityManager instance also functions as a factory for Query instances, which are used to execute database queries . Every JPA implementation provides classes that implement | |
BIRT/ODA ObjectDB Driver The ObjectDB BIRT/ODA driver is an extension for the open-source Business Intelligence and Reporting Tools (BIRT). It adds support for ObjectDB as a data source and JPQL as a data set query language ... ) and click Next . Enter a JPQL or a JDOQL query and click Finish . See the Report Generation with BIRT and JPA tutorial for more detailed instructions. | |
Step 4: Create an ObjectDB Data Set Queries against the database are represented in BIRT as data sets. To create the data set: Open ... this tutorial contains Point entities. We will use a simple JPQL query that retrieves points with x value in ... and paste to enter the above query and click Finish . When the data set is created successfully | |
Step 3: Define an EJB Session Bean getAllGuests() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return query .getResultList(); } } The GuestDao session bean (EJB) class defines two methods | |
Step 3: Define a Spring DAO Component() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return query .getResultList(); } } The GuestDao Spring component class defines two methods: persist | |
Step 3: Define a Spring DAO Component getAllGuests() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return query .getResultList(); } } The GuestDao Spring component class defines two methods: persist | |
[ODB1] Chapter 2 - A Quick Tour, step by step. Both sample programs are contained in ObjectDB's samples directory. 2. 1   ... of the second run is expected to be: Hello World 0 Hello World 1 After two runs, the database contains a list of two strings "Hello World 0" and "Hello World 1 ". Program Source Code The program consists |