About persist


Wrong data stored in time only fields

This may be related to the fix for the problem described in this thread: Wrong data stored in date 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. ... 18:18:14" ) ) ; em. persist ( dt ) ; } catch ( ... 21:26:19" ) ) ; em. persist ( dt ) ; } catch ( ...


Database(*.odb) file size on disk

Hello, we have questions about the file size of ObjectDB database on disk. Can you tell us something about how the deleting of entities affects the size of *.odb files on disk? -Will the released memory always used by new entities? -Will be the database file automatically reduced?   We have created a small test, in which we create and delete entities. It looks like that the released memory are reused but the the file not resized. The database is at the end empty again, but larger than the initial size. ... of entity: " + entity . id ; em. persist ( entity ) ; entityAIds. add ( ...


Need help to make this test work and define proper annotations for entities Lists

Hi, I can't get this simple test case to work, i know it is probably due to the lack of proper annotations on entities list, could anyone help me to define them? NB in this test case I didn't set all entities methods for the sake of clarity, also in actual application no field are public nor static and no entity is static.    ... ord. customer . name ) ; em. persist ( ord ) ; em. getTransaction ( ... Cascading of the persist operation from OrderDat to CustomerDat is missing. Try: ...


Database connection url

I'd like to run a database called db1.odb on port 6136, and simultaneously open it in the explorer. I left the conf file set as: <server> <connection port="6136" max="100" /> <data path="$objectdb/db-files" /> </server> However, I'm not sure about the connection url for the code, and for the explorer. I tried this: Transactor.emf = Persistence.createEntityManagerFactory ("$objectdb/db1.odb"); #1 2010-11-11 07:26 I'd like to run a database called db1.odb on port 6136, and simultaneously open it in the explorer. I lef ...



Persist enumerated type property or field as a string.(Enum Constant of javax.persistence.EnumType)


Strange Error with Criteria API and Sorting

We're creating a simple selection (distinct) including an order clause. When watching the created criteria in debugger we get the correct expression: SELECT DISTINCT $1 FROM MyEntity $1 WHERE ((TYPE($1)=class test.MyEntity)) ORDER BY UPPER($1.name) DESC You can see that in the order by there's correctly a "$1" var. Running this (without the type thing before) in the explorer correctly returns the sorted results. However, running this with the criteria API produces this error: ... ( "Name A" ) ;   em. persist ( o1 ) ; em. persist ( o2 ) ; em. persist ( o3 ) ; ...



Persist enumerated type property or field as an integer.(Enum Constant of javax.persistence.EnumType)



(Optional) The name of the persistent field or property of the associated entity that is used as the map key.(Annotation Element of javax.persistence.MapKey)



Provides access to the metamodel of persistent entities in the persistence unit.(Interface of JPA)


objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property) The following is a detailed report on investigation of multiple issues that have been mentioned in the following forum postings and issue reports (but please do not visit them from here now, the diagnostics there are now obsolete): - Issue #282 - ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection ... one way of checking the enhancement. - Attempts to persist the Project (which under some circumstances gives errors). This ... Result: on persistence an error occurs: Persist project.. Exception in thread "main" [ObjectDB 2.6.9_02] ...