About recording

forum_thread

Objectdb recovery

Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power outage). We are using following configuration: <recovery enabled="true" sync="false" path="." max="128mb"/> <recording enabled="false" sync="false" path="." mode="write"/> Is there any possibility of data loss when power outage? ... path = "." max = "128mb" / > <recording enabled = "false" sync = "false" path = "." mode = ...

 
forum_thread

wrong query result

Hi we have a problem with queries, database is returning wrong results. These are the queries we run from ObjectDB explorer. #1 2014-01-30 11:04 Hi we have a problem with queries, database is returning wrong results. These are the queries we run from ...

 
forum_thread

significant performance decrease

we are using objected in embedded mode (on OS X and WINDOWS). The database increased now to around 400000 entities of one class (database file size around 1.5 GByte). The response time of standard queries increased with this database size to an unacceptable rate (several seconds compared to around 30% when the number of entities was just half of the current). We tried to optimize the cache settings, current objectdb.conf is: <!-- ObjectDB Configuration --> <objectdb> ... path = "." max = "128mb" /> <recording enabled = "false" sync = "false" path = "." ...

 
issue

Best practice for history tracking

We would like to add to records start and end timestamp fields. When end field is null, it indicates the last version of this item. Few questions: JPA Feature Version: 1.04 Priority: Normal Status: Closed Replies: 1 Type:  JPA Feature ...

 
forum_thread

Uninitialized primary key (id = 0)

Exception in thread "main" [ObjectDB 2.2.9_04] javax.persistence.RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (image.Meta:0) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) I check the db by explorer.jar, and find the only one record is id=0. What situation will be id=0? TIA #1 2011-08-26 05:26 Exception in thread "main" [ ObjectDB 2.2.9_04 ] javax. persistence . RollbackException Fai ...

 
forum_thread

Handling "is null" in where clause

Greetings, I was playing aroung with JPQL and have found that there is a problem with "is null" queries. When you use "is null" in where clause, query runs correctly, but results are incorrect. Let me show you an example: - entity @Entity public class EntityA { @Id Integer id; Integer simpleField; (getters and setters here) - populating database #1 2010-09-24 10:23 Greetings, I was playing aroung with JPQL and have found that there is a problem with "is null" queries. ...

 
manual

JPA Query Structure (JPQL / Criteria)

Explains the structure of a JPQL query, which consists of 6 clauses: SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY. The syntax of the Java Persistence Query Language (JPQL) is very similar to the syntax of SQL. Having a SQL like syntax in JPA queries is an important advantage because SQL is a very powerful query language and many developers are already familiar wi ...

 
forum_thread

ObjectDB version 2.2 has been released

ObjectDB 2.2 has been released and it includes important additions and fixes: ... Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug ( issue #36 ...

 
forum_thread

java.sql.Timestamp.getTime() not working

Hi, I need to work with Timestamp diff in two entity fields, but this queries SELECT count(p) FROM Player p WHERE p.loginAt.getTime()-p.registeredAt.getTime()>:value SELECT p.loginAt.getTime() FROM Player p fails with object is not an instance of declaring class but SELECT p.loginAt.getYear() FROM Player p works. How that possible?   #1 2016-11-27 19:51 Hi, I need to work with Timestamp diff in two entity fields, but this queries SELECT count ( p ...

 
issue

Server crash - Mismatch client-server protocol prefix

We've been having a problem where our ObjectDB server goes unresponsive every 2 days or so.  I've reviewed the server-side logs, and there are no events logged shortly before the crash.  Once the server gets in this state, it is unresponsive to bin/server.sh restart; I have had to reboot the entire server on which it's running.  The only recorded symptom is a client-side error (which fortunately gets auto-mailed to me): Bug Version: 2.5.2 Priority: High Status: Closed Replies: 4 Type:  Bug ...