ObjectDB Database Search

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

, MONTH , DAY , HOUR , MINUTE , and SECOND parts from a date or time value. For example: YEAR({d '2011 ... ({t '23:59:00'}) returns 23 . MINUTE ({t '23:59:00'}) returns 59 . SECOND({t '23:59:00'}) returns 0 ... ", Integer.class, time); Expression minute = cb. function (" minute ", Integer.class, time); Expression second = cb. function ("second", Integer.class, ts);

,HOUR_OF_DAY=19, MINUTE =14,SECOND=43,MILLISECOND=31,ZONE_OFFSET=0,DST_OFFSET=3600000], java.util ... ,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=7,HOUR_OF_DAY=19, MINUTE =14,SECOND=43,MILLISECOND ... _OF_YEAR=150,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=7,HOUR_OF_DAY=19, MINUTE =14,SECOND=43

. MINUTE , 0);         cal.set(Calendar.SECOND, 0);    ... (Calendar.HOUR_OF_DAY, 0);         cal.set(Calendar. MINUTE , 0);  

number is printed. There is a 1 minute delay set. The same as 1, but keep ObjectDB's connection open ... again. Important: do all that until a new number is printed. There is a 1 minute delay set. The same as 1

(Trying again.  Last post, ~50 minutes to compose, failed, possibly due to an attachment upload size limit being exceeded before the post attempt.  =(  ) I desire to have my persistent objects be cached until the Java Virtual Machine (JVM) does a full Garbage Collection (GC

when trying to execute in explorer (max heap size 1GByte) delete from LogEntry l it comes up with a Java heap error after 20 minutes of executing. How to empty such a table ?     hgzwicker Hans-Georg Zwicker This may be because the transaction size is limited by the heap size

for full redeployment of large web applications that take many minutes to fully redeploy. (No, this is not an ad

Kocks Here the same, a few minutes later. 6,6GB Maybe a problem with GC? Thanks in advance Priiiiil

We are for a some time using joining the thread ODB-IndexActivation to prevent issues when accessing database without the index been ready. Original Thread: https://www.objectdb.com/forum/2401 Now we've run into issue, that in some database the Index rebuild takes a lot of time (e.g. 20 minutes

). Code is straight forward, and attached - it was written in about 3 minutes so please disregard the 'in

;  calendar.set(Calendar. MINUTE , 0);         calendar.set

query needs 4 to 5 minutes to return a result. I have been adviced to use indexes

10: 335544 24159168 com.objectdb.o.QRQ Here is the jmap at time1 + 1 minute : num #instances #bytes

Our application has some complex entities. We do batch update(merge detached entity) every 2 minutes . We find the period significant IO costs these days, and disappeared when turn off the batch updating. 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly

(); } It may take some time for this process to complete (about 20-30 minutes on your sample database ... ))   version 2.8.3 query plan (query takes minutes ): Query plan 1/16 description

;threadPoolExecutor.awaitTermination(3, TimeUnit. MINUTES );     factory.close(); After 3 minutes the EntityManagerFactory is closed with all its EntityManager instances

(); em.close(); emf.close(); } It may take some time for this process to complete (about 20-30 minutes