ObjectDB Database Search
151-200 of 200 resultsApache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found) Hello, ObjectDB team! I am struggling with getting ObjectDB 2.5.0 to work with clean Apache Tomee 1 .5.2 with transaction-type="JTA". I don't have any configurations in Tomee (objectdb.jar is in ... application failed: C:\Users\Mircea\Documents\NetBeansProjects\natural7\target\natural7- 1 .0-SNAPSHOT | |
JPA 2.1 and AttributeConverter Hello :-). Are there any plans to support JPA 2. 1 ? I would wish to have a support for @AttributeConverter. Bot01 Frantisek Novak The general plan is to support future versions of JPA so probably JPA 2. 1 features will also be supported. support Support Thanks for the answer. And is there current | |
ObjectDB version 2.1 has been released ObjectDB 2. 1 has been released and it includes important additions and fixes: Added Online Backup utility ( issue #16 ). Added Master-Slave Replication / Clustering (issue #17 ). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects | |
Verify Error with Java 1.7 ObjectDB enhanced classes fail when compiled to Java 1 .7 [ObjectDB 2.2.9_08 Enhancer] 28 persistable types have been enhanced: ... com.vaisala.jx.db.gdm.model.SourceType stack trace from jUnit test com.vaisala.jx.db.gdm.facade.BaseFacadeTest Time elapsed: 0 sec | |
javax.transaction.Synchronization with Java SE 10.0.1 (using Java SE 10.0. 1 ). So I tried to track down why it is not found via runtime and discovered | |
ObjectDB Unable to process 1.6 L records. Hi I have a db of around 1 .6 lakh records. But now am getting some unexpected error when accessing some of the entities. And when am fetching all the records using objectdb explorer its showing exception. I have diagnosis the db with objectdb doctor but not find any error. Please check | |
Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not foundNot Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found | |
query only reports 1 result 2.7.2_01 suddenly some queries do only have 1 result even there are more results (you can use the database that you have from #308): this query gives 1 result even there are a lot more: select o from ObjectNode o where o.classIdentifier = '(OP)' and o.state = 98 and o.type = 0 and o | |
ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6. 1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush. | |
New Java 8 (JDK 1.8) Collection Methods ObjectDB version 2.5.5 (and above) supports Java 8 (JDK 1 .8). Tracking changes to collections and maps using some new Java 8 methods is currently not fully supported. The main known issue is that orphan removal does not happen as a result of removing a reference to an object | |
Typo in ObjectDB 1.0 Manual Support Knowledge Base ObjectDB 1 .0 Manual Chapter 7 "JDOQL Queries" Section 7.2 "Query Filter Syntax" Subsection "Fields" Second to last sentence Remove "not" from that sentence. "An attempt to access a field or invoke a method using a null reference results in a false evaluation | |
ObjectDB 2.5.1ObjectDB 2.5.1 | |
JPQL Subqueries (JPA 1.0)JPQL Subqueries (JPA 1.0) | |
ObjectDB 2.9.1ObjectDB 2.9.1 | |
ObjectDB 2.6.1ObjectDB 2.6.1 | |
ObjectDB 2.3.1ObjectDB 2.3.1 | |
ObjectDB 2.0.1ObjectDB 2.0.1 | |
ObjectDB 2.8.1ObjectDB 2.8.1 | |
version 2.4.5+ with GlassFish 3.1.2, errors when runs application. Version 2.4.4 worked but not 2.4.5 or laterversion 2.4.5+ with GlassFish 3.1.2, errors when runs application. Version 2.4.4 worked but not 2.4.5 or later | |
ObjectDB 2.4.1ObjectDB 2.4.1 | |
ObjectDB 2.7.1ObjectDB 2.7.1 | |
ObjectDB 2.1.0ObjectDB 2.1.0 | |
JPQL Update & Delete (JPA 1.0)JPQL Update & Delete (JPA 1.0) | |
Integration with Java EE (JPA 1.0)Integration with Java EE (JPA 1.0) | |
jakarta.persistence.metamodel.EntityType of the given name is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set ... of the managed type. Since: Jakarta Persistence (JPA) 1 .0 Class getBindableJavaType () Return the Java ... . Since: Jakarta Persistence (JPA) 1 .0 BindableType getBindableType () Return the bindable type | |
jakarta.persistence.PersistenceConfiguration of this PersistenceConfiguration class should use sharedCacheMode . Since: Jakarta Persistence (JPA) 1 .0 JDBC_DATASOURCE An instance of javax.sql.DataSource . Since: Jakarta Persistence (JPA) 1 .0 JDBC_DRIVER Fully qualified name of the JDBC driver class. Since: Jakarta Persistence (JPA) 1 .0 JDBC_PASSWORD Password for JDBC | |
jakarta.persistence.criteria.Subquery Parameters: name - alias Returns: selection item. Since: Jakarta Persistence (JPA) 1 .0 Expression ... Persistence (JPA) 1 .0 Expression cast ( Class type ) Cast this expression to the specified type, returning ... of the containing query Returns: subquery root. Since: Jakarta Persistence (JPA) 1 .0 Join correlate ( Join | |
jakarta.persistence.metamodel.IdentifiableType Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Inherited from ManagedType Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... . Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return | |
jakarta.persistence.metamodel.MappedSuperclassType. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Inherited from ManagedType Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... type. Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return | |
Auto Generated Values. It takes a name, an initial value (default is 1 ), and an allocation size (default is 50). A sequence ... ="seq", initialValue = 1 , allocationSize =100) public class EntityWithSequenceId { // Use ... . This means that if you want sequence numbers to start with 1 when using the TABLE strategy, you must specify initialValue=0 in the @TableGenerator annotation. | |
Server User List to connect to the server only from the specified IP addresses. For example, "127.0.0. 1 " (the local computer ... of "192.18.0.0-192.18.194.255,127.0.0. 1 " allows connections from any IP address in the range 192.18.0.0 - 192.18.194.255 and from 127.0.0. 1 . The admin attribute, with a value of true or false , specifies | |
jakarta.persistence.EntityManager StoredProcedureQuery EntityManagerFactory Since: Jakarta Persistence (JPA) 1 .0 The JPA Connections and Transactions ... . Since: Jakarta Persistence (JPA) 1 .0 void close () Close an application-managed entity manager ... : IllegalStateException - if the entity manager is container-managed. Since: Jakarta Persistence (JPA) 1 .0 boolean | |
jakarta.persistence.TypedQuery.setParameter(Parameter,Date,TemporalType)-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.TypedQuery.setParameter(String,Calendar,TemporalType) argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.TypedQuery.setParameter(String,Date,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.TypedQuery.setParameter(Parameter,Calendar,TemporalType): Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.TypedQuery.setParameter(int,Calendar,TemporalType) argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.TypedQuery.setParameter(int,Date,TemporalType) argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(int,Calendar,TemporalType) of the query or if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(int,Date,TemporalType) if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(Parameter,Date,TemporalType). Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(String,Calendar,TemporalType) or if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(String,Date,TemporalType) if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(Parameter,Calendar,TemporalType) of the query. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.Query.setParameter(int,Date,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.Query.setParameter(String,Calendar,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.Query.setParameter(String,Date,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.Query.setParameter(int,Calendar,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/time types defined in java.time . Since: Jakarta Persistence (JPA) 1 .0 | |
jakarta.persistence.metamodel.ManagedType the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return the attributes of the managed type. Returns: attributes of the managed type. Since: Jakarta Persistence (JPA) 1 .0 ... Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name ) Return the Collection-valued | |
jakarta.persistence.metamodel.EmbeddableType is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0 Set getAttributes () Return ... type. Since: Jakarta Persistence (JPA) 1 .0 CollectionAttribute getCollection ( String name , Class ... of the given name and type is not present in the managed type. Since: Jakarta Persistence (JPA) 1 .0 |