8 | java.sql.Time field off by 30 minutes settings. Maybe there is a problem when the time offset includes half a hour (e.g. UTC+05:30 |
8 | ObjectDB CRUD Examples take several hours but may save later much more. This is especially important if you do not have prior |
8 | Possible issue with timestamps. All other hours seem to be fine. Thankfully if I do: select c from CDI c where c.creationDate > :startDate and c |
8 | Spring Data JPA - PersistenceException thrown successfully. watchdogtimer Tom Hartwell After a few hours of debugging, I found that the MetaModel |
8 | Vacuum - Reclaiming Unused Space In Odb down for a couple of hours so we are investigating other strategies such as the Doctor utility. CAPdev CAP |
8 | Query filter comparing Dates the database as time (e.g. in milliseconds) since 1.1.1970 UTC. For TemporalType.DATE the hours |
8 | ObjectDB size not reducing production. I do an hourly backup and the backup file is not any smaller(it gets bigger) each hour as |
1 | Memory leak in com.objectdb.o.CST) and see if there's a performance difference. Trianglehead Json Error Just an update, after a couple hours of using latest |
1 | each 1-2 days objects on some objectdb level lock/block each other. Maybe the activity is lower just because it was evening / night and not peak hours |
1 | Unexpected error when loading all entity instance using the Doctor. Then running the application for like 5 hours and now I have a corrupted database file |
