About version

181-190 of 200Refresh
Issue
1

each 1-2 days objects on some objectdb level lock/block each other

queries without any object manipulation in these threads we how have compiled with the 02 version ... to cause issues. The change in ObjectDB version doesn't look related, it may be simply the exact ... " /> version
Forum
1

500Mb ObjectDb database opening issue

/23/2016 15:38:42.3842: INFO : (AppMain.java:34 thread:main): main(): Java version used:1.8.0_66x32 ... thread:main): main(): Java version used:1.8.0_66x32 1/23/2016 15:42:35.4235: INFO : (AppMain.java:35 ... :23.4923: INFO : (AppMain.java:34 thread:main): main(): Java version used:1.7.0_79x32 1/26/2016 20
Forum
1

Failed to read DB file while online backup is running

to finish its task. The version of ObjectDB I am running is 2.6.1.b02 Any idea what is causing ... will be observing it with the new version. Unfortunately the "Failed to read from file '/path_to_db/dbFile.odb ... order to explore this issue, including range of affected ObjectDB versions. I finally got
Forum
1

problems using the explorer

we are currently evaluating objectDB. Environment OSX 10.9.2, JavaSE-1.7 Version: Kepler Service ... > com.objectdb objectdb <version>2.2.5version> ...   Problem: we created a small example that just writes and retrieves
Forum
1

Recommendation - concurrent access multiple class v

that it might get corrupted because the manual says that we must not access ObjectDB with different versions ... , where the previous version of a class is used by some servers, then others come with the new version, then finally all of them get the new version? So...basically...concurrent access with version x and version x
Issue
1

Unexpected exception (Error 990) on find

exists in previous versions (2.4.7, 2.4.6). If it is a new problem, we may be able to track the change ... for a item thats not in the db.   The problem is in version 2.4.7. I will try with an older Version ... -Length. Hi, the ObjectDB Doctor says:   ObjectDB Doctor [version 2.4.7_16] Copyright (c) 2013
Forum
1

Wrong @Id type

UPDATE queries that was fixed. Please see this forum thread. Which ObjectDB version are you using? Try the last ObjectDB version, which should fix this issue/ To repair IDs that have already changed their types you will have to 'touch' the objects and store them again, or use an ObjectDB version
Forum
1

Wrong data stored in time only fields

.persistence.Temporal; import javax.persistence.TemporalType; import javax.persistence.Version ... ;         private Long version;         private Date startDateTime;     // Time stamp: start of recording ... other = (DateTime)o;             return id.equals(other.getId()) && version.equals(other.getVersion
Forum
1

Possible cause for "Enhancement of type ... is old and cannot be used"

objectdb.jar library version that the program runs with. I am certainly not 'adding a persistent field to a super class' in any of these cases. I have not yet tried versions between objectdb-2.6.3_04 ... of my objectdb-based programs using a version later than objectdb-2.6.3_04 (other than the very basic ObjectDB
Forum
1

@MappedSuperclass and @Transient not working as I expected

javax.persistence.Version; @MappedSuperclass public class DataObject { @Id @GeneratedValue protected int id; @Version protected long version; @Transient protected EntityManagerFactory emf ... + " version " + version);   EntityManager em = emf.createEntityManager();   em.getTransaction