ObjectDB Database Search
1-50 of 102 resultsApache License, Version 2.0, January 2004" shall mean any work of authorship, including the original version of the Work and any modifications | |
JPA Entity Fields Inverse ( mappedBy ) fields Primary key (ID) fields Version field The first three groups (transient ... . However, the last two groups (primary key and version fields) can be used only in entity classes. Primary key ... accessed. Version Field ObjectDB maintains a version number for every entity. The initial version | |
Optimistic locking: prevent version increment on entity collection attribute relationship) with an optimistic locking strategy supported by a version field. Is it possible to prevent the increment of the version of entity E when entities are added to or removed from the collection ... the version . Otherwise the version will be updated, and currently you cannot disable this update | |
Database is erased after deploying a new web application version within Tomcat and uses ObjectDB. Each time I upload a new version of the web ... it: When running a new web application version , I get an exception saying this file could not be opened ... version and then deploy the new one. Something still keeps this file open and preventing the new | |
version 2.8.9_06 significantly slower for queries compared to 2.8.9we tried (you have our example database form former issues) the latest version , did a statics ... .objectdb.com/forum/2845 for queries we are using hgzpincher Hans-Georg Zwicker Version 2.8.9_01 ... in version 2.8.9_02 but maybe there is another relevant query performance regression | |
database version Is there some way of telling, just from an obd database file, what version it is? dmoshal David Moshal An ObjectDB 2.x database file has no version , at least from the point of view of ObjectDB users. You should be able to use the same database file with different versions of the ObjectDB 2.x software. support Support | |
deadlock with newest version 2.4.4_16deadlock with newest version 2.4.4_16 | |
Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01) | |
Database Management Settings The version -check attribute of the element specifies whether optimistic locking is enabled. Optimistic locking is fully automatic and enabled by default in ObjectDB, regardless of whether a version field is defined in the entity class. Some ORM JPA providers require a version field. You can disable | |
jakarta.persistence.EntityManager within the persistence context and the lock mode type is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic version checks when obtaining the database lock ... - if an unsupported lock call is made. OptimisticLockException - if the optimistic version check fails | |
jakarta.persistence.LockModeType.OPTIMISTIC on a versioned object, the entity manager must ensure that neither of the following ... of type LockModeType.OPTIMISTIC_FORCE_INCREMENT on a versioned object, will also force an update (increment) to the entity's version column. The persistence implementation is not required to support | |
jakarta.persistence.MappedSuperclass protected Integer empId; @ Version protected Integer version ; @ManyToOne @JoinColumn(name = "ADDR ... to FTEMPLOYEE.EMPID // Inherited version field mapped to FTEMPLOYEE. VERSION // Inherited address field ... _EMP.EMPID // Inherited version field mapped to PT_EMP. VERSION // address field mapping overridden | |
jakarta.persistence.metamodel.IdentifiableType.getDeclaredVersion(Class) to the version attribute declared by the entity or mapped superclass. Parameters: type - the type of the represented declared version attribute Returns: declared version attribute. Throws: IllegalArgumentException - if version attribute of the type is not declared in the identifiable type. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.metamodel.IdentifiableType.getVersion(Class) SingularAttribute getVersion ( Class type ) Return the attribute that corresponds to the version attribute of the entity or mapped superclass. Parameters: type - the type of the represented version attribute Returns: version attribute. Throws: IllegalArgumentException - if version attribute | |
jakarta.persistence.PersistenceUnitUtil ) Return the version of the entity. A generated version is not guaranteed to be available | |
jakarta.persistence.metamodel.SingularAttribute.isVersion() Jakarta Persistence (JPA) Method in jakarta.persistence.metamodel.SingularAttribute boolean isVersion() Is the attribute a version attribute? Returns: boolean indicating whether the attribute is a version attribute. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.metamodel.IdentifiableType.hasVersionAttribute() Jakarta Persistence (JPA) Method in jakarta.persistence.metamodel.IdentifiableType boolean hasVersionAttribute() Whether the identifiable type has a version attribute. Returns: boolean indicating whether the identifiable type has a version attribute. Since: Jakarta Persistence (JPA) 1.0 | |
Possible cause for "Enhancement of type ... is old and cannot be used" sure the enhancement script runs the same objectdb.jar library version that the program runs with. I ... yet tried versions between objectdb-2.6.3_04 and objectdb-2.6.6_07 (bracketing to find which one broke it). But I know that I can't run any of my objectdb-based programs using a version later | |
jakarta.persistence.Convert would otherwise apply. The Convert annotation should not be used to specify conversion of id attributes, of version | |
jakarta.persistence.Converter never applies to id attributes , version attributes , relationship attributes, or to attributes explicitly | |
jakarta.persistence.Entity of the entity. An entity class may optionally have a field or property annotated Version , which holds | |
Eclipse/JPA Spring MVC Web Tutorial This is the Eclipse version of the Spring MVC and JPA tutorial. It demonstrates how to create and run a full Java Spring MVC (Model View Controller) web application in ... .6.1 but it should work with other Eclipse versions as well (dialog boxes and menus might look | |
How to Use a SF with extended Persistence Context? get this stack: 13:52:01,121 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 13:52:01,304 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 13:52:01,347 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 13:52:01,959 INFO [org.xnio] XNIO Version 3.0.3.GA 13 | |
Mismatch client-server protocol prefix:757) I checked multiple times if the versions match. They do. DB server version 2.6.2. Client version 2.6.2. Also there's only one objectdb jar on the classpath. It's also not a network problem ... if different ObjectDB versions are in use on the client and on the server, but such exceptions | |
Installing a VM security fix leads to inactive DB objectdb version . We had to create new keys multiple times because of the unstable activation ... stability issues have been fixed in version 2.9.3 and there are no new known issues. If you create a new activation using version 2.9.3 or later and still have issues (except when the MAC addresses | |
Problem on JPA Merge Entity.. Please try version 2.0.5 that fixes the problem. support Support Thank you for your reactivity. I try the last version monday and i give you feed back. guli CHARLOIS Hi, I try the version 2.0.5 ... the bug is still there. Do you check if the new version fixes the problem on the test | |
Activation error on Schema change the configuration of the server. Version 2.3.7 is more strict in checking this. support Support That explains ... . Even when objectdb.conf with old license key where copied to new version directory. No schema change, no application modification just migration to new ODB version . lwalkowski Lukasz Walkowski Sorry | |
OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011) and activations in recent versions . Please make sure that your classes are OEM enhanced. See this forum thread ... on that computer, are there other changes except the ObjectDB version (e.g. Java version )? What happens if you try earlier ObjectDB versions now? support Support I have attached two ObjectDB logfiles | |
Getting Unexpected internal exception when updating entity in MEM db The stack trace indicates using an old version of ObjectDB (which?) Please try and check if the error happens also with the last version . support Support Hi The stack trace indicates using an old version of ObjectDB (which?) I am using Objectdb-2.8.2. Thank you. Deepak_1996 Deepak Kumar | |
Guestbook example from tutorial does not work..Provider Server version : Apache Tomcat/7.0.55 Server built: Jul 18 2014 05:34:04 Server number: 7.0.55.0 OS Name: Linux OS Version : 3.13.0-37-generic Architecture: amd64 JVM Version : 1.8.0 | |
zip file or JAR manifest missing; my office pc use 2.2.4, report no error. It seems the last version has something with it. gzdillon ... "); SingleManager.clearDB("URI"); new PageTest().read(); } } the version 2.2.8_6 can not pass, saying "use the same prime key" something. and version 2.2.9_3 passed, but with the message | |
Spring MVC and JPA Tutorial an ObjectDB database. This tutorial is available in the following versions : In addition, the demonstrated application is available as a Maven project: | |
Not releasing locked MST object that the issue exist in version 2.9.3_01 it would help. Although a deadlock is not mentioned in the change log since version 2.8.3, there is always a chance that an issue happens only in specific versions | |
IDs of Entities suddenly became UUIDs? by your application. Please check that you have only one version of every entity class, since that problem may be caused by having different versions of the same entity class (e.g. one with  ... . support Support Actually, we're only having one version of our entities for sure which are using a Long | |
StackOverflowError after commit.o.ENT.D(ENT.java:417) btc_es BTC EmbeddedSystems What version of ObjectDB are you using ... version 2.6.4.b04 btc_es BTC EmbeddedSystems Please recheck the version number (on the client | |
UTF Error version , 2.8.8, on both the server side and the client side? If you still get this exception with version 2.8.8 please post the up to date stack trace. support Support The Client side is 2.8.8 (a maven project) . The downloaded version of ObjectDB is also 2.8.8. I have added the full error | |
Update Entity references if we change the type of an entity option to version 1.7.0_02, which can be enabled by setting a system property before accessing ... disabled. support Support Hello, the version with the new property can't not be used. We get exceptions ... the requirements for a stable version . Will they be a more elegant solution in the long term? We think we need | |
Disable Evaluation possibility Hello, we are now using quite old version , so I am sorry, if something changed in the meanwhile we have not yet had time to test newer version . Is it possible somehow to disable Evaluation completely, for example via some argument for ObjectDB server, or you could create separate jar | |
Too many objects for this ObjectDB Edition if anyone has encountered a similar problem. I had been using an older version of ObjectDB but have switched to a newer version and am still getting the error. Any help would be much appreciated, Thanks | |
GlassFish 3.1.2.2/JBoss 7.1.1 but it is unknown yet when (meanwhile previous versions of JBoss 7 could be used). Apparently ... is expected anytime soon? Unfortunately, using the older version of the server won't work | |
ways to recover from DB curruption Hi, I have a database file which was mistakenly opened by a different version of my entities model and is now not usable any more. When I try to open this file using explorer or even running ... the previous version of the class? Thanks, Eitan eitane Eitan Eibschutz Try opening the database in | |
Duplicate Entity class names causes Exception in Query); } return c; } @Id protected String id = "1"; @SuppressWarnings("unused") // used by JPA @ Version private int version ; @Basic protected java.lang.Integer lastInstance; public void generateItems(EntityManager | |
combined index not used is much more complex and could easily be inaccurate. Future version of ObjectDB will probably ... Support we implemented version 2.8.0_02, added:   ... query: ( version 2.7.6 it takes 47 ms, version 2.8.0_02 it takes 700 ms): SELECT DISTINCT o.parentNode | |
javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName priority, it is inconveniencing my work the most. webel Dr Darren Kelly Have you tried version 2.2.6_01 that might fix it (see #2)? support Support I tried version 2.2.6_01 and it did NOT fix ... (Thread.java:680) webel Dr Darren Kelly Upgraded issue tracking version to 2.2.6_01 webel Dr Darren Kelly | |
DISTINCT key causing internal exception on 2.6.4.b10.key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2.6.1.b06 Harman ... and you will see no problems with this query Second, I have attached a) Screenshot for used ObjectDb version b) Original ... an incomplete repair of another issue in build 2.6.4_09. Version 2.6.5 should work well. support Support | |
NullPointerException in __odbGetNumMember field version using enhanced method version is annotated with @ Version quasado Alexander Adam Okay | |
UTF Error. Please advise whether this only happens when you use different versions of ObjectDB on the client and the server (2.8.4 and 2.8.5_06). Does upgrading to the same version , 2.8.5_06, on both the client ... protocol these versions of ObjectDB are not compatible to be used together in client-server mode.  | |
Server crash - Mismatch client-server protocol prefix Schreiber Since you are probably using the same ObjectDB version on the client and the server ... both are result of a change in your system or upgrading an ObjectDB version ? support Support The connection ... versions of ObjectDB can at least produce a better error message in this case. support Support | |
ArrayIndexOutOfBoundsException on flush ( ~2KB) are handled differently and many problems in early versions of ObjectDB 2.x where related ... these exceptions. Please keep it for checking against future ObjectDB versions (until this problem | |
retrieval again and again started period of time. This happens in all versions hgzpincher Hans-Georg Zwicker The problem ... version , active at the customer, keep you informed hgzpincher Hans-Georg Zwicker Hi, since nearly 2 |