ObjectDB Database Search

has _odbTracker field added) So, instead of DB write a standard serialization mechanizm is triggered. Finnally ... (and stack trace if available).  So, instead of DB write a standard serialization mechanizm

Hi, I use windows 7 64 bit version. When I'm trying to open the ObjectdB explorer I get this windows error: "Failed to find Java VM".   What is the problem? dreckguy Ophir Haramaty Have you tried both explorer.exe and explorer-b.exe ? Can you write it from the console : java -jar explorer.jar

of Contact and Customer in the database, which have to be converted to Address instances, you will have to write some conversion code. support Support

you for your answer and help. Two short follow-up questions: You write that trying to access a removed

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

Hi, we are using ObjectDB 2.4.6_10 (embedded mode). The pre-registration of a data type (see below) fails because ODB can't create a new file in a non-existing folder hierarchy. The user under which the JVM is executed in which the code below is run does have write permissions on the folder

.UserException: Failed to write the value of field field com.btc.ep.architecture.virtualcomposed.bl

.getPersistenceManager() On server it keeps writing  SSL Error: Unsupported or unrecognized SSL message

Hi, one of my DB files can not be open by neither DB explorer, nor the DB Doctor. Both are writing same mistake : ObjectDB Doctor [version 2.5.6_05] Copyright (c) 2014, ObjectDB Software. All rights reserved. ------------------------- No errors have been found ------------------------- com

return for this help. Possible help includes developing open source tools, writing (tutorials

I tested ObjectDB. When I write JPQL, I get this error. Caused by: com.objectdb.o.InternalException: Error reading UTF string at com.objectdb.o.BYR.U(BYR.java:1217) at com.objectdb.o.BYR.U(BYR.java:523) at com.objectdb.o.BYR.L(BYR.java:504) at com.objectdb.o.QJD.a(QJD.java:241) at com.objectdb.o

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

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

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

We have an unexpected output "*** PatternParameterImpl" in our java console. Do you know why? Caused by: PrintStream. write (String) line: 603 PrintStream.print(String) line: 745 PrintStream.println(String) line: 882 ThreadPrintStream.println(String) line: 179 TYS.k() line: 199 TYM.Z(boolean

above ( write a 10-15 Mbytes) need to check remaining memory in any available profiler. Stack trace

Hihi, I'm wondering if this is a bug. I have a simple entity with java.sql.Time field. On writing and readback, the field is found to be 30 minutes off. It is observed on objectdb explorer as well. Timestamp works perfectly fine. Ps. dont think its a UTC issue. My system is set at far off UTC

the configuration when an active transactions is preparing to write updates to the database

{ ... } After this change the app starts, it only reads the objects, no writing happens

the query parameter as TemporalType.TIMESTAMP . But when I write following query: Query q = JPA.em

Good day! I wrote some JUnit tests that create separate objectdb databases and exercise the entities therein (via read/ write operations). The tests run fine individually, but when I run "all tests," one fails consistently with the message: com.objectdb.o._JdoUserException: Object 'actr.model

); } } Is there a way to get data of all classes without writing down 10 different queries (i.e. using the for loop

I have some code that, before writing an object via ObjectDB makes a query to ensure the new object is different from what's already stored.  The problem is that, before any instances of that object have been stored, the query generates an exception.  I'd been expecting 

then it is interpreted as the path on the server machine to which to write the backup file and no temporary file

version of ObjectDB and extract the zip file. Make sure that everyone has read/ write /execute permissions

disk storage consists of a RAID5 of 4x 2TB SAS-SSDs and brings a write and read performance of 4

the location of the log files to another path. Or: Grant the ObjectDB process permission to write to: C

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

it. There is some handling of the exception like writing it into the log file with trace level

We are decided to move our products from 2.6.1.b06 to 2.8.4, could you confirm that new objectDb 2.8.4 is fully compatible with many already created databases based on 2.6.1? So, it means that we need to be sure that new objectDb 2.8.4 could read/ write to databases created by 2.6.1. Please confirm

for the reply.  Why is write limited to master ?  arunjoy Arun Joy An architecture

repeating activations on upgrades, but unless you write code to automate activations (i.e. run

;   }     } Trianglehead Json Error The default behaviour is to delay writing

. While writing it i found out that it only happens whén I use the enhancer at compile time. I

when it will be fixed, but you can use the workaround of writing several lines of code to update the database after adding a new field. support Support

. This could be caused, for example, if the database is stopped (abnormally) during a writing action, and recovery

annotated with @Startup can access the database OK for both read and write , suggesting that the orm.xml

this architecture, write operations have to be directed to the master, where read operations

. If it is "all" you can save a lot of space (and improve performance) by switching to the " write " mode

updated. This should be fixed in future versions. The workaround is to write some code (even in

the vacuum. If there is no way to do this other than manually implementing code to read, delete, and write

/ write to disk mechanismns ? We have hundreds of clients  communicating to our core process

. We can release a new build with writing relevant information to the log when it happens in order

with a server-based database - 2 writing to the db, one reading. I had added an index to a property

and just writing the condition to a log file, because if the database connection is closed, further attempts to close it are not necessary. support Support

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

.8.5_04 which should work better. support Support OK Thanks I will try it and write back on results

writing an interceptor annotation that logs all exceptions. Without this interceptor the log file

after retrieving the BeitragVertragArt class, changing some fields and writing it back? The fix in _14

had operations resize.  It didn't have write permissions; permission added and ODB Doctor is working