ObjectDB Database Search
101-150 of 200 resultsobjectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation objectdb- 2 .6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property ... there are now obsolete): - Issue #1924 - ObjectDB- 2 .6.9: Failed to commit transaction: Failed ... the system, just for Expert System cases). To make things simpler, this posting will examine only these 2 cases | |
JPA 2.0 Criteria API: (When) Fully supported ? An excerpt from the website of a 3rd party vendor which tries to support JPA 2 .0: "The primary difference between JPA 1.0 and JPA 2 .0 implementations is how data is fetched: the JPA 1.0 implementation creates a JPQL query string for fetching while the JPA 2 .0 implementation uses Criteria | |
2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object" ObjectDB 2 .7.3_03 gives my application a "com.objectdb.o.UserException: Attempt to modify ... ; (ObjectDB log file attached.) If I revert to ObjectDB 2 .7.3, then no more exception. (No other code ... image that shows the error is attached.) CBE CBE This is probably caused by a change in version 2 .7 | |
Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x seconds in object db 2 .x I have build the query using the follwoing Query query = persistanceManager ... objectdb explorer binitbhaskar Binit Bhaskar ObjectDB 2 .x is usually faster than ObjectDB 1.x, so it should be possible to get at least similar performance for this query with ObjectDB 2 .x. Maybe | |
objectdb:2.8.4 - Error occurred during initialization of boot layer_UPDATE_JDK9\JavaApps\CommonThirdParty\mockito\objenesis- 2 .1.jar;D:\Projects\Anritsu\Perforce\ws_alexander.golyshkin_ALL\DEV\RTD_7_6_0_JAVA_UPDATE_JDK9\JavaApps\CommonThirdParty\mockito\cglib-nodep- 2 . 2 .jar ... \comfyj- 2 .4.jar;D:\Projects\Anritsu\Perforce\ws_alexander.golyshkin_ALL\DEV\RTD_7_6_0_JAVA_UPDATE | |
after upgrade to 2.9.0 database destroys, urgent issue at our most important customer, production shutdown after upgrading to 2 .9.0 (because of the other problems in former versions), the database destroys ... (if you had schema changes in addition to upgrading to 2 .9.0) . If this is the only issue then running ... the engine that manages the database storage, at least in the last 2 years, so there is nothing in version 2 | |
OutofMemory error with Object DB 2.0 Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2 .0 The application works fine with only 256MB heap size with objectdb 1.0 But on 2 .0 even with max heap ... PersistentManager is used to begin the transaction. With objectdb 2 .x do we need to close the  | |
Explorer in 2.3. Then allow import of that file into another database. 2 . Lazy loading of data, especially in table view ... evaluation. For me, #1, # 2 and #3 would be the most important. Also, I've found some small bugs: 1 ... 'recent connections'. 2 . When editing a field in an @Embedded object, I get an error message | |
Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity a non-static logging variable holder can be used in an @Entity. ObjectDB 2 .6.3_04 Apache Log4j2 - 2 .5 Mac OS X   ... ): [ObjectDB 2 .6.3_04] Failed to process class file of type 'com.example.SubEntity' (error 422) com.objectdb.o | |
Upgrade to 2.4.1_01 Hi, We tried to upgrade from 2 .3.7_18 to 2 .4.1_01 to pickup some fixes. We discovered that our code no longer works when using 2 .4.1_01. We did some probing and found one thing. I have attached ... our code for 2 .3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER | |
UserException - Object User#2 belongs to another EntityManager Hi! Scenario's steps: 1. User goes to his profile, a JSF page. 2 . @RequestScoped CDI bean ... .pingushare.entity.p1.User# 2 ' belongs to another EntityManager at com.objectdb.o.MSG.d(MSG.java:61) Why does this error happen, because there 2 independent transactions? I guess | |
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 ... more It seems that there is something wrong with persistent context. it seems that glassfish 3.1. 2 behaves differently. I ... to persistent unit lazily. however, glassfish 3.1. 2 immediately after deployment of application logins | |
ObjectDB internal error on 2.6.4.b10 for query with DISTINCT I observed that on new ObjectDb v. 2 .6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $ 2 JOIN $ 2 .values $1 WHERE ($ 2 .namespace == 'com.anritsu.pa3.ttcn3' AND $ 2 .key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2 .6.1.b06 | |
Unable to convert 1.x odb file to 2.x Hi, my company is just about to switch from ObjectDB 1.04.2487 (SE) to ObjectDB 2 . So I downloaded the objectdb- 2 .5.5_02, activated it with our licence, enhancing went ... - 2 .0 file conversion Exception in thread "main" java.lang.RuntimeException: Internal Exception | |
ObectDb 2.3.6 in OSGi environment use a persistence.xml! The stacktrace looks like this: [ObjectDB 2 .3.6] javax.persistence ... .runners.ParentRunner$ 2 .evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements ... ) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$ 2 | |
Logical Operators in JPQL and Criteria API Logical operators in JPQL and JPA criteria queries combine simple Boolean expressions to form complex expressions. Logical operators ObjectDB supports two sets of logical operators, as shown in the following table: Set 1: JPQL / SQL Set 2 : Java / JDO AND && OR || NOT ! JPQL uses SQL notation | |
JPA Metamodel Types The Jakarta Persistence (JPA) Metamodel API defines a structured hierarchy of interfaces and enumerations to represent the persistent types within a domain model. Metamodel Types Hierarchy in Jakarta Persistence (JPA) 3. 2 Base type definitions The core abstractions of model types | |
JPA Extended API Reference Guide Jakarta Persistence API (JPA) 3. 2 documentation, generated from the official JavaDoc and enriched with practical notes. It groups the API types into logical sections to help you locate core concepts, query facilities, metamodel details, configuration options, annotations, and exception information | |
Retrieving JPA Entities the Level 2 (L2) cache, if enabled. JPA then adds the new entity to the persistence context as a managed | |
JPA Named Queries their named queries by using the JPA 2 Metamodel interface. For example: em. getMetamodel (). managedType | |
DELETE Queries in JPA/JPQL As explained in Chapter 2 , you can delete entities from the database by following these steps: Retrieve the entities into an EntityManager . Remove these objects from the EntityManager within an active transaction, either explicitly by calling the remove method or implicitly through a cascading | |
JPA Core Types and inheritance relationships. Jakarta Persistence (JPA) 3. 2 Core Types Bootstrapping and Configuration | |
Defining a JPA Entity Class. The values of these fields are stored in the database when an entity is persisted. Chapter 2 provides | |
JPA Criteria Queries queries: Criteria Queries Hierarchy in Jakarta Persistence (JPA) 3. 2 Instances of  | |
JPA Query API Jakarta Persistence (JPA) represents queries with two interfaces: the Query interface, which was the only query interface in JPA 1, and the TypedQuery interface, which was introduced in JPA 2 . The TypedQuery interface extends the Query interface. Use the Query interface primarily when the query | |
Comparison in JPQL and Criteria API Most JPQL queries use at least one comparison operator in their WHERE clause. Comparison operators ObjectDB supports two sets of comparison operators, as shown in the following table: Set 1: JPQL/SQL Set 2 : Java/JDO Less Than Less Than or Equal To = Equal To = == Not Equal To != The main | |
UPDATE SET Queries in JPA/JPQL You can update existing entities, as explained in chapter 2 , by following these steps: Retrieve the entities into an EntityManager . Update the relevant entity fields within an active transaction. Apply the changes to the database by calling the commit method. JPQL UPDATE queries provide | |
JPA Persistence Unit (PersistenceConfiguration) Starting with JPA 3. 2 , it is no longer mandatory to use a persistence.xml   | |
Managing JPA Entities EntityManager . ObjectDB also manages a level 2 (L2) shared cache for the EntityManagerFactory | |
JPA Criteria FROM and JOIN is structured as follows: Criteria Query From Components in Jakarta Persistence (JPA) 3. 2   | |
ObjectDB Overview - managed only by standard Java APIs (JPA / JDO 2 ). Extremely fast - faster than any other JPA / JDO | |
ObjectDB Website - Terms and Conditions of Use applicable copyright and trade mark law. 2 . Use License Permission is granted to temporarily download | |
Database Server the server with no arguments displays the following usage message: ObjectDB Server [version 2 .9.4 | |
JPA Primary Key ( long ). The primary key of the first entity is 1, the second is 2 , and so on. Primary key values | |
jakarta.persistence.criteria.Root Persistence (JPA) 2 .0 The FROM clause (JPQL / Criteria API) article explains how to use Root ... of the given basic type. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Expression value ... . Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Object value ) Create a predicate to test | |
jakarta.persistence.criteria.From to the type. Since: Jakarta Persistence (JPA) 2 .0 Public Instance Methods Selection alias ( String name ... ) 3. 2 Predicate equalTo ( Expression value ) Create a predicate to test whether the expression ... against Returns: predicate testing for equality. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo | |
objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active' objectdb- 2 .6.9_06 NetBeans8.1+Glassfish4.1.1 Mac OS X Possibly related: How to Use a SF ... .test.mini.ejb.ExtProjectBuilder ! Then Clean and Build (objectdb- 2 .6.9_06.jar is already included ... All_ , not shown.) The following strategy used to work for objectdb- 2 .4.0_05 , but fails | |
jakarta.persistence.criteria.Subquery. A subquery has an expression as its selection item. Since: Jakarta Persistence (JPA) 2 .0 Public ... of the given basic type. Since: Jakarta Persistence (JPA) 3. 2 Root correlate ( Root parentRoot ) Create ... for equality. Since: Jakarta Persistence (JPA) 3. 2 Predicate equalTo ( Object value ) Create | |
ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection The following error is reported for objectdb- 2 .6.9.jar: Failed to commit transaction: Failed ... (error 613) Did not happen with objectdb- 2 .6.3_04 (which one can easily test and compare in the test ... : (all classes within entity packages): javac.classpath:lib/objectdb- 2 .6.9.jar [ObjectDB 2 .6.9 Enhancer] 8 | |
each 1-2 days objects on some objectdb level lock/block each other each 1- 2 days we have the situation that our system changes to a completely underperforming mode ... is much more critical, today we switched back to 2 .7.5, but the same behaviour - nothing changed in ... % and around 200 threads hgzwicker Hans-Georg Zwicker According to the subject of this thread it happens every 1- 2 | |
2.9.x query issue with @Unique constraint Query doesn't return results in versions 2 .9.x when there's a unique property in (where/and .. or ... for :userName parameter 2 .8.9 Query plan description ============================ [Step 1] Scan type User locating all the User (u) instances. [Step 2 ] Evaluate fields in User (u) instances. [Step 3 | |
jakarta.persistence.PersistenceUnitUtil Persistence (JPA) 2 .0 Public Instance Methods Class getClass ( T entity ) Return the concrete entity ... cannot be loaded from the database. Since: Jakarta Persistence (JPA) 3. 2 Object getIdentifier ( Object ... is found not to be an entity. Since: Jakarta Persistence (JPA) 3. 2 boolean isInstance ( Object entity | |
[ObjectDB 2.3.7_25] Unexpected exception (Error 990) copy... [ObjectDB 2 .3.7_25] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64 ... :163) at com.objectdb.Doctor.main(Doctor.java:22) [ObjectDB 2 .3.7_25] null lorenz2304 Benjamin Lorenz There is a problem with 2 Person instances, apparently in their salt byte[] array | |
DISTINCT key causing internal exception on 2.6.4.b10 I observed that on new ObjectDb v. 2 .6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $ 2 JOIN $ 2 .values $1 WHERE ($ 2 .namespace == 'com.anritsu.pa3.ttcn3' AND $ 2 .key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2 .6.1.b06 Harman | |
[ObjectDB 2.5.6_05] Unexpected exception (Error 990) server] [ObjectDB 2 .5.6_05] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_25 (on Windows 2003 5. 2 ). Please report this error on http://www.objectdb.com ... .java:145) at com.objectdb.o.TSK.f(TSK.java:95) [2014-08-24 02:49:35 #34 server] [ObjectDB 2 .5.6_05 | |
[ObjectDB 2.6.9] Unexpected exception (Error 990) [2017-03-29 14:04:44 #1 client] [ObjectDB 2 .6.9] Unexpected exception (Error 990) Generated ... problem.. version 2 .5.6_05 - size of data 100GB I am running a Doctor in prod (in a backup file, It takes long time...), . PRODUCTION [2017-03-30 07:04:53 #37 server] [ObjectDB 2 .5.6_05] Unexpected | |
New issues with queries using build 2.7.6_08 Unfortunately Build 2 .7.6_08 caused exceptions in a lot of system tests of our test suite which still ran successfully with Build 2 .7.6_07. 1. For example following query returns 3 verdict objects ... AND execution.execRecordID = record.uid AND record.executionConfig = config AND config.uid = '23A' 2 | |
[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 ... /1107 support Support Build 2 .7. 2 _01 should fix this bug. support Support Build 2 .7. 2 _01 has a side effect that introduces another bug ( issue #2142 ). Build 2 .7. 2 _02 should be used. support Support | |
Step 6: Set the Spring XML: spring org.springframework.web.servlet.DispatcherServlet 2 spring *.html 30 index.jsp The settings | |
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 dragging a Table from the [Palette] window and dropping it on the report design (.rptdesign) layout. Set the column number to 2 , number of details to 1 , select the data set (e.g. Points by X |