8 | Storing Images/UML2. to persist the images, i just store an array of bytes (byte[]) representing the encoded images. i.e. a class which has a field of type byte array. to turn the bytes into an image, i use a UI ... there's an easier way. so, yes, the equivalent of blobs (byte arrays) are supported well. andrewmcveigh Andrew |
8 | @OneToMany(fetch = FetchType.LAZY) list is always null containing another one (OneToOne) entity with a byte[] array without calling the getter of the array of the child entity, the array becomes null. public class ByteData { // ... id private byte |
7 | 500Mb ObjectDb database opening issue500Mb ObjectDb database opening issue |
7 | Replication error on slave restart="true" /> <dirty-tracking arrays="false" /> </entities> <schema> </schema> <server ... always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities |
7 | Strange behaviour with ORDER BY and IN de.solvit.objectdbtest.entity.Location; import java.util.Arrays; import java.util.List; import java ... final List<Location> locations = Arrays.asList( new Location("1", "A"), new Location |
7 | PersistenceException: Failed to locate field always = "true" on-persist = "true" on-commit = "true"/> <dirty-tracking arrays = "true ... " on-commit = "true"/> <dirty-tracking arrays = "true"/> </entities |
7 | member visiting in jpql? TIA gzdillon Lai Yang The length field of arrays is not supported by JDOQL / JPQL queries. You may maintain an ordinary int field (holding the array length) for this purpose. support Support |
7 | EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable="true" /> <dirty-tracking arrays="false" /> </entities> <schema ... -tracking arrays="false" /> </entities> <schema> </schema> <server |
1 | [ObjectDB 2.3.7_25] Unexpected exception (Error 990) There is a problem with 2 Person instances, apparently in their salt byte[] array. There was a change in the way byte[] arrays are stored in ObjectDB. In theory this should not affect existing databases |
1 | Page #9 entry 0 (key 'bjjl') has 75 extra bytes / Unexpected last index ID: -119 (expected -116) storing arrays in a bad format - exploring it requires a way to reproduce the database creation ... and there was a false alarm of the Doctor in checking byte arrays. Build 2.4.1 fixes this problem. support Support |
