Internal Website Search

EmbeddedSystems The 2nd level cache stores object data ( byte []) rather than live entity objects ... ;2nd level cache as object IDs (PK) encoded in the  byte [] of a MyEntity1 instance

= 'vanova' 5.  = null - byte [1110] 6.  = 'SmartTablePreference -  - eu.extech.quant ... .  = null - byte [422] 6.  = 'SmartTablePreference -  - eu.extech.quant.dashboard.recent

baURI is a byte []; JP QL select e.baURI.length from URI e where id=82778 JP QL [ObjectDB 2.2.9_04] javax.persistence.PersistenceException Navigation from ' byte []' through 'length' is invalid (error 763) at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:636) at util.JPQLcmd.QureyCMD(JPQLcmd

#instances # bytes class name ---------------------------------------------- 1: 704422 950869896 [B 2 ... 10: 335544 24159168 com.objectdb.o.QRQ Here is the jmap at time1 + 1 minute: num #instances # bytes

more details about the byte [] allocations? Who holds them? What is the common size of the byte [] that fills

optimizations I meant JIT Compiler optimizations and not Java compiler optimization, i.e. the byte code ... relevant byte code after enhancement. support Support  Have you tried build time enhancement

Marko You can store large attachments in ObjectDB as byte [] fields. The database size is limited to 128 TB (= 131,072 GB = 134,217,728 MB). There is no limit on object sizes, but byte [] is limited by

; byte [] macBytes = ni. getHardwareAddress ();      if (macBytes != null & amp

and columns, but you are right - transient fields consume space in the database only for their definition (several bytes ) but not for their values. support Support

class per element type. You can also store an entire non parsed XML file as string or byte [] in one entity object. support Support

byte [] by reducing required storage space. Removed a shutdown hook that leads to memory leak ( issue

the field of byte [], you know. TIA gzdillon Lai Yang 1, It is supposed that there is an implicit index

. I've chosen to use the additional field option as it should only contribute an extra 20 - 24 bytes

Hi,     Does ObjectDB support "stored procedure"?     Some frequent operations may be finished within DB, client just get a few bytes of the result. TIA gzdillon Lai Yang No stored procedures in ObjectDB. JPA (or JDO) lifecycle events can be used as a replacement

at defineClass call in d method ACL class which is triggerd by i method of STL class. I think the byte array

data (such as images) in byte [] . Enhancement is usually more efficient (even though assignment

and without, the object that JVisualVM showed as the biggest memory user was byte arrays - usually

field for the File or URL and convert it from/to byte [] or String in JPA lifecycle events methods

persisted entity objects?   Fields of arbitrary objects (like key-value store)? Pages as byte

%) 18003496 (13%) byte [] 18.0291352369998 351112 (18%) 83005789 (59.8%) com.objectdb.o.SLV 16

is loaded as byte []  to save space, and extracted into objects only when needed, but that loaded

bytes ). confirmed that problem is resolved when the recovery files are deleted, does'nt seem to be any

parsed XML file as string or byte [] in one entity object. Every method has its pros and cons so it depends on your specific needs. support Support

that do byte code enhancements missing the external dependencies. I guess I should have stated

. It is unclear why the byte code of an ObjectDB class was posted, if it contains relevant information

Java Proxy. - JAXB add some JAXBAccessor into the byte code. - Google guava cache do some CGLIB

;       H.print();         byte

, including transient. The 2nd level cache keeps only the data from the db as byte [] , so transient

seems to contain a byte [] object ( i observed that it represent some data of my entities beans ). xirt Sylvain

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

: last destination index 2203995484 out of bounds for byte [2147483639]         ... .ArrayIndexOutOfBoundsException: arraycopy: last destination index 2203995484 out of bounds for byte

;           byte [] hardwareAddress = ni ... ;   byte [] hardwareAddress = ni.getHardwareAddress();       

" occupies 375,301,672 (17.92%) bytes . The memory is accumulated in one instance of "com.objectdb.o.MST ... .58%) bytes . These instances are referenced from one instance of "com.objectdb.o.PAG[]", loaded by

keys are slower. If possible, try to avoid primary keys longer than 32 bytes (in the test they seem to be 36 bytes ). support Support Thanks for the fix. Also thanks for the hint with long keys

this problem. support Support Currently across the application it can be a string or a byte []. In this particular database it should always be a byte [] and the db is not replicated. Understood about the test

" field is a byte []. This worked ok in 2.3.3_06. felixobjectdb Richard Szurgot Thank you for this report

bug in the default fetch policy. Fixed a new bug in retrieving byte [] ( issue #624 ). Fixed a bug in

). Improved persisting byte [] by reducing required storage space. Removed a shutdown hook that leads

small / large objects. ObjectDB splits large objects ( 2000 bytes ) into pages. Somehow the stack

Fixed a bug of  duplicating new objects during merge . Fixed a username/password issue in using EntityManagerFactory 's getMetamodel . Fixed a bug in detachment of hollow objects on close ( issue #799 ). Fixed a Doctor exception ( issue #796 ). Fixed a Doctor bug in checking byte [] arrays

Fixed a bug in queries on embedded objects in C/S mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code enhancement in Java EE server. Fixed a bug in multi variable queries.

, which is part of one large ObjectProperty object of 2699 bytes that was divided to two database

destination index 2155981072 out of bounds for byte [2147483639] at java.base/java.lang.System.arraycopy

#11436 entry 3 (key '41zbT') has 134 extra bytes [7] Unexpected exception in page #11436 entry #4

program and repairing it. The problem was in cleaning continuing sections of large objects ( 1980 bytes

the Explorer (on the Schema tab) about the space in bytes that each entity type consumes (for storing