ObjectDB Database Search

Is there a way to show the executed Sql/Jpql in the console? wua Andreas Wurm You can set the log element in ObjectDB configuration to write logging also to the console:      ... to the console. To write query execution to the log, add the following logger element to the configuration

Sandeep Dhamale Currently, migrating data between ObjectDB and other data stores requires writing ... have to write java module with JPA to retrieve entity and then using some kind of ORM or direct JDBC persist

server and not for the slave server. To save space please try limiting recording to write operations ... something is blocking ObjectDB from writing changes and transactions to the disk. So the master database is not

) PS. Now I'm writing from IE. zmirc Mircea Chirac To check if this is a cache issue ... neither. I restarted the machine as well, but nothing. I'm writing thanks to IE now. zmirc Mircea Chirac

Hello, I just wanted to write another anotation to my key field so I can have a really simple index. This is the original code: @Entity public class ObjectDbEntity implements DataItemProvider ... to perform massive reads? ksii13 E ObjectDB is faster than other DBMS, not just in writing but also in

Hi, it happened already few times (seemingly randomly), that some db operation (read and also write ) failed with an exception during an online backup of the same DB file was running and was close ... the mistake is happening only when the DB read/ write happens during the online backup (as described

happens? It could happen if during writing a pure date (with no time) to the database the TimeZone ... ) and the change of the offset is between these write operations, i.e. different levels of the BTree

a table before erasing the content. Thanks. Linuski christophe LASKAWIEC You will have to write code for this purpose. Use enhanced classes to get best performance in reading and writing the objects

. ObjectValue ID:=100, TYPE:=Person, REVISION:=0, isPersisted:=true, LockMode:=PESSIMISTIC_ WRITE ... . ObjectValue ID:=100, TYPE:=Person, REVISION:=2, isPersisted:=true, LockMode:=PESSIMISTIC_ WRITE

Hello, I'm currently writing a program using JavaFX and ObjectDB and I'm encountering a problem with Entities not sending their updates to each other. I have two Entities in question at the moment ... didn't know how to make it possible to persist them in ObjectDB. Due to this, I've chosen to write

is one of your classes. ObjectDB doesn't support writing the enhanced classes back to a JAR file, so you have to specify a destination path for writing the enhanced classes as class files ( using -d ), and of course

supported by ObjectDB for existing objects? If it is, do I have to write the "embedded-only" clausule also to the child classes or is it sufficient to write it on their predecessor ? Is this only a bug

We have an application that runs on a single server in embedded mode to write server million records.  Is it possible to use the single server license for embedded mode use?  I've looked ... server that needs to write the number of records over the evaluation limit, it doesn't seem to fit

.getTransaction().begin(); Account a1 = em1.find(Account.class, 0, LockModeType.PESSIMISTIC_ WRITE ); a1 ... _ WRITE // try to retrieve again EntityManager em2 = emf.createEntityManager(); em2.getTransaction

I am trying to implement a database using ObjectDB. To get started i want to write Entities of Type RequirementDBEntity into a database. I followed the tutorials here but when launching the program ... ."; } And my code for actually writing to the database is: import javax.persistence.*; public class

a write (or flush) from the database.obj$ file to database.obj during an opened database connection ... the EntityManager ) the  odb$ file still exists?  b) is there a way to automatically force a write

Request for a new JDO manual, covering ODB 2. dmoshal David Moshal Please subscribe to the ObjectDB 2 JDO Manual issue. Because writing a new manual and then maintaining two similar manuals, one for JPA and the other for JDO requires massive work, this will be done only if there is a sufficient demand. support Support

Solano Martinez At the moment porting data from ObjectDB to another database requires writing

I'm writing a multi-user drawing tool, using objectdb as the central store.  When a user press F5, I want to pick up all the changes from the database.  So, I call evictAll() in the following ways: pmf.getDataStoreCache().evictAll(); // the factory pm.evictAll(); // the persistence

. If you can write and upload a simple test program that demonstrates the problem it could help.  

Hi, I was rewriting our DAO to support pagging in large dataset and I think I have found a problem with sorting. I send you a test case - sorry for using the same project as previous, but it was faster to write this test case. As usual, you can load data with DataLoader and then check problem

Hi, Is it possible to write a JPA query to select objects that contain a collection of elements? For example, suppose I have a table that maps a search terms to pages: @Entity public class SearchIndex { @Index SearchTerm term; @Index Page page; } Now suppose I have an array of SearchTerm objects

writing ). Every mechanism has its own advantages and disadvantages. In some cases recording is faster

you will have to migrate it by yourself. This can be done by writing a small JPA program that retrieves entity

, the records at the end continuously purge as the new ones come in(duplicate write , one to in-memory

can write up an example if you still have problems.   Erick erick.rosas Erick Hi again,   Thanks

to ObjectDB you will have to write your own conversion program. If you use JPA with MySQL you can retrieve old

up to be a part of the new enterprise persistence standard, the writing was on the wall for JDO. People

I have a question about partial indexing. For example, a field of String type ttt, will be distinguished by the first 5 characters, then I can make a index of substr(ttt,1,5) in MySQL. With ObjectDB, how can I write the annotation for this purpose? TIA gzdillon Lai Yang Currently ObjectDB supports

I found the message: Error opening zip file or JAR manifest missing: /E:/projects/ObjectDB/bin/objectdb.jar Some of projects can read the DB, but others can not read or write the DB. Exception in thread "main" [ObjectDB 2.2.5] javax.persistence.PersistenceException Type ItemList is not found

Hi all,   Honestly, I'm fairly new with JPA2 Criteria queries - but as far as code effort goes, it has saved me a bit of pain. I'm writing a dynamic query builder (only 1 level deep for basic entities) - but  even though I get most queries to work, I am getting the following error

will be locked for WRITE by pm1 and exception is expected when pm2 tries to read the same object (on 

. After re- writing the test for odb/eclipselink (same test, different EMF) the exact same behaviour is observed. I

on package.jdo file, this approach has advantage to writing constructors by hand, we skiped fields

.jsp there are polish chars) But in this way I'm unnable to write polisch chars just on the site

/ writing to objectdb. The issue occurs just once during our test, other instances of this enhanced class ... : for single read/ write /update/delete: - we create new EntityManager, do the operation in transaction

such entity class could be either accessible for READ or for both READ and WRITE . More ideas and feedback ... might be to look at it in terms of CRUD as opposed to READ/ WRITE . ThreaT Ashton Hogan

(when clearly they are). [EDIT: This was because the NetBeans Run and Ant were over- writing the enhanced ... was over- writing the post-compile enhanced class files. I switched to only running from the console

the wrapper, which writes them to it's log file.  The stack traces do show that the Exceptions ... / write threads are terminating abnormally, I'm not sure how our application is reacting

cannot correctly write back into the database file, is it possible that the db log file remains in the file ... is enabled and there is a failure in writing to the database file, ObjectDB repairs the database file

During an write to an embedded database, objectdb gets stuck.  It won't progress from this point, even after a day of waiting. I include a stack trace from jvisualvm: at java.lang ... are mixed and not ordered by age, even though writing to the log file is synchronized by ObjectDB

because of incompatible stream serialVersionUIDs and mismatched .odb$ write files.  Is this a supported upgrade ... . and mismatched .odb$ write files. When a database is closed correctly you should not have an .odb

) is:          It should force physically writing to the recovery file before starting to write to the database file. Although the default,  sync="false

- this feature might enable using ObjectDB as a performance booster, with almost no need to write new

The new ObjectDB Manual describes how to use ObjectDB 2 with JPA. An additional manual that focuses on using ObjectDB 2 with JDO can help JDO users. But since writing a new manual and then maintaining two similar manuals, one for JPA and the other for JDO requires massive work

and LockMode set to PESSIMISTIC_ WRITE . This results in the exceptions below. Could you advise on the errors

and relationships as and when needed. We do not want to write 1000s of dedicated projection

Hi, I'm running objectdb in server mode, config as it comes out of the box. In this case the database is being used as a queue with multiple seperate processes, each with multiple threads, writing messages. The message is split into a lightweight metadata message to allow fast searching

in criteria queries . Fixed a "Failed to write the value of field property" bug. Fixed a 

on such attempt it writes to the log an error message ("Negative snapshot user count") with a stack trace