About byte
JPA Persistable Types
Explains how JPA manages types, including entity classes, embeddable classes, primitive types, wrappers, string, date, enum, collections and maps.... Primitive types: boolean , byte , short , char , int , long , float and double . ... classes from package java.lang: Boolean , Byte , Short , Character , Integer , Long , Float and Double ...
Database Schema Evolution
Explains how ObjectDB handles automatically schema changes.... numeric type. In this context numeric types are: byte , short , char , int , long , float , double , Byte , Short , Character , Integer , Long , Float , Double , ...
transform(loader, className, classBeingRedefined, protectionDomain, classfileBuffer)
Invoked when a class is being loaded or redefined.(Method of javax.persistence.spi.ClassTransformer)
Storing Images
What is the best way to store images? As external files? In the database as blobs? Are blobs supported?... 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 toolkit called HCIL ...
getByteField(pc, field, currentValue)
Return the value for the field.(Method of javax.jdo.spi.StateManager)
setByteField(pc, field, currentValue, newValue)
Mark the field as modified by the user.(Method of javax.jdo.spi.StateManager)
javax.jdo.spi.PersistenceCapable
A class that can be managed by a binary-compatible JDO implementation must implement this interface.(Interface of JDO)
Database size is much larger than expected (x2)
I store images into objectdb. The schema is : <URI>::=(<sUrl>, <cMark>, <iSize>, <baBody>, <id>) <sUrl>::=String <cMark>::=char <iSize>::=int <baBody>::=byte[] <id>::=@ID So simple a class will fail after 155,648 insertions with -Xmx1432m, ... char <iSize> ::= int <baBody> ::= byte [ ] <id> ::= @ ID So simple a class ... check your code, especially the conversion of images to byte[] - maybe unintentionally it duplicates the required space. I ...
javax.jdo.spi.StateManager
This interface is the point of contact between managed instances of PersistenceCapable classes and the JDO implementation.(Interface of JDO)
PersistenceCapable.READ_WRITE_OK
If jdoFlags is set to READ_WRITE_OK, then the fields in the default fetch group can be accessed for read or write without notifying the StateManager.(Static Field of javax.jdo.spi.PersistenceCapable)