ObjectDB ObjectDB

Internal Website Search

11-20 of 200 resultsRefresh

Does run time enhancer due to GlassFish/Payara do anything that would affect loaded compile-time entity classes ?

ObjectDB support wrote elsewhere: ... you do not need the Enhancer agent, since you use build time emhancement, but GlassFish invokes it automatically. Currently there is no setting in ObjectDB to disable the enhancer agent ... Q: Does run time enhancer due to GlassFish/Payara

find() cost unreasonable time!

, why? Result: =========== find time @ 24.125000 getSons time @ 0.000000 1 : type:Nodes, sons:2 child : 2 child : 3 Iterator time @ 0.000000 find time @ 0.000000 getSons time @ 0.000000 2 : type:Nodes, sons:2 child : 4 child : 5 Iterator time @ 0.000000 find time @ 0.000000 getSons

Date field Index is corrupted due to time change

to neutralize the effect of the current time zone, keeping the values order, etc. Hopefully build 2.6.5 ... is very basic, simple (I guess): We create a 1G DB file when the application starts for the fist time ... . only one DB operation runs at any one time. The load never exceeds more than 5 transactions per 10

java.sql.Time field off by 30 minutes

time. rwaters Richard Currently there is no known bug that may cause this. Maybe it is related ... Hihi, I'm wondering if this is a bug. I have a simple entity with java.sql.Time field. On writing ... you for the test case. Here is a revised version that also prints the default time zone (and with some fixes

Wrong data stored in time only fields

only fields. The object and its date and time fields are the same as in the referenced thread. Except we are using ObjectDB 2.6.4_08, the system time zone is set to EST and both the OS and JVM are using the 2015g time zone data. While we cannot see a problem with date only fields (more testing

Time Sequence Object Command DB

We (www.s2ssystems.com) have a time-sequential object command database. I would like ... are: Each transaction has a time-stamp which is the time the transaction was added to the database. The user can efficiently restore the data-model to a specified time which requires reloading

java.lang.NoClassDefFoundError: java/time/LocalDate

ObjectDB version 2.8.3 (which adds support of Java 8 date and time types) you have to use Java 8 or above, rather than Java 7 that you are currently using. support Support ... .objectdb.o.InternalException: java.lang.NoClassDefFoundError: java/time/LocalDate java.lang.NoClassDefFoundError: java/time/LocalDate at com.objectdb.o.VUT.<clinit>(VUT.java:71) at com

Insert time increases as db grows.

; then 11 seconds and so on. Should I change my config in some way to get more stable insertion time ... after every commit, to avoid further performance loss over time. support Support Well, I'm using Spring Data JPA ... the same results: insertion time grows as db grows. 4410 Arsenii I've just set enhancer as javaagent

Retrieve latest entry in a time-series

As mentioned elsewhere, subqueries are not currently supported. A subquery is the way that seems recommended to get only the latest entry in a time series (e.g. the latest time-clock entry for all employees). Is there an ObjectDB way to get the latest entry in a series? jshaffstall Jay Shaffstall

Open several objectdb databases the same time

' that is currently in use by another process (error 141) at com.objectdb.jpa.EMF ... @2015-09-17_12.08.15\TC_9_2_3_1_8b@2015-09-17_12.08.15.pa3' that is currently in use by ... one process at a time. The server mode is designed for accessing a database by several processes

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support