ObjectDB Database Search
101-150 of 200 resultsjakarta.persistence.AttributeConverter
class must be annotated Converter or declared as a converter in the object/relational mapping ... and properties of the target type. The Convert annotation may be used to apply a converter
|
|
What role is the JDO in ObjectDB?
indexes is currently missing in JPA. It be added in JPA 2.1. Meanwhile - use JDO annotations ... annotations for indexes. So if your application is based on JPA - the only place in your code ... to other JPA providers by adding their @Index annotations , e.g. @javax.jdo
|
|
Migration problem
; import lombok.Getter; import lombok.Setter; import org.hibernate. annotations .ColumnDefault; import org ... . annotation .CreatedBy; import org.springframework.data. annotation .CreatedDate; import org.springframework.data. annotation .LastModifiedBy; import org.springframework.data. annotation .LastModifiedDate; import org
|
|
jakarta.persistence.GeneratedValue.generator
TableGenerator annotation which declares the generator. The name defaults to the entity name of the entity in which the annotation occurs. If there is no generator with the defaulted name, then the persistence
|
|
jakarta.persistence.EntityGraph
the name of a named EntityGraph (an entity graph defined by means of the NamedEntityGraph annotation , XML
|
|
jakarta.persistence.TypedQueryReference
Jakarta Persistence (JPA) Interface jakarta.persistence.TypedQueryReference Type Parameters: - an upper bound on the result type of the query A reference to a named query declared via the NamedQuery or NamedNativeQuery annotations . See Also: EntityManager.createQuery(TypedQueryReference
|
|
jakarta.persistence.AccessType
Jakarta Persistence (JPA) Enum jakarta.persistence.AccessType java.lang.Object ∟ java.lang.Enum ∟ jakarta.persistence.AccessType Implemented Interfaces: Constable , Comparable , Serializable Used with the Access annotation to specify an access type to be applied to an entity class, mapped
|
|
Should I use ObjectDB and JDO?
;relational databases). I want to use annotations , which seems to mean JDO 2.1+ is required. Does ObjectDB support JDO annotations ? I don't see an ObjectDB tutorial using JDO and annotations . Is there one? I searched for books for JDO and only found 3, and they are 13
|
|
Embedded Entity in EmbeddedId not persisted. Error 631 at select.
1: Works not: if field AId.b is not @Embedded annotated . * * case 2: Works: if field AId.b is @Embedded annotated . * *   ... ; question: Is @Entity annotation of class B not sufficient enough, or *  
|
|
Spring + Maven + persitence.xml
.springframework.web.servlet.mvc.method. annotation .ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96) org.springframework.web.servlet.mvc.method. annotation ... .servlet.mvc.method. annotation .RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter
|
|
Spring Data JPA - PersistenceException thrown
.context. annotation .CommonAnnotationBeanPostProcessor.autowireResource(CommonAnnotationBeanPostProcessor.java:461) at org.springframework.context. annotation .CommonAnnotationBeanPostProcessor.getResource(CommonAnnotationBeanPostProcessor.java:435) at org.springframework.context. annotation
|
|
A bidirectional OneToOne association with a shared primary key
Hi, In Hibernate, it is possible (using Hibernate specific annotations ) to define a  ... all of the required annotations on the respective Entities and any special initialization calls that need ... annotations . You can have a bidirectional one to one association, but it cannot be based on identical primary
|
|
JPA inheritance issue with ObjectDB - Field not found in type error
. I've also tried using the @MappedSuperclass annotation instead of the @Inheritance annotation ... This was an error I introduced by erroneously using @ihneritance annotation . This is the response I got in ... ; You annotated your sub-classes with @Inheritance which is the opposite of what the doc says
|
|
Problem with @UniqueConstraint
It seems there is a problem with @UniqueConstraint. Same annotations using hibernate works fine ... ) String name; } } pezi Peter Sauer @UniqueConstraint is an ORM annotation . It references RDBMS ... @Index / @Unique annotations (hopefully in next versions) - you will have to use JDO @Index
|
|
Does ObjectDB support @Parent for @Embeddable reference to parent?
/Embeddables#Example_of_an_Embeddable_object_ annotations @Entity public class Employee { .... private ... well, but get methods should be annotated when using property access, rather than the annotated fields, as ... of setter trick seems to work. Thanks. but get methods should be annotated when using property access
|
|
jakarta.persistence.PersistenceContexts.value
Jakarta Persistence (JPA) Method in jakarta.persistence.PersistenceContexts PersistenceContext[] value (Required) One or more PersistenceContext annotations . Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.metamodel.StaticMetamodel.value
Jakarta Persistence (JPA) Method in jakarta.persistence.metamodel.StaticMetamodel Class value Class being modelled by the annotated class. Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.TableGenerator.name
Jakarta Persistence (JPA) Method in jakarta.persistence.TableGenerator String name (optional) A unique generator name that can be referenced by one or more classes to be the generator for id values. Defaults to the name of the entity when the annotation occurs on an entity class or primary key
|
|
jakarta.persistence.Table.uniqueConstraints
and JoinColumn annotations and constraints entailed by primary key mappings. Defaults to no additional
|
|
jakarta.persistence.IdClass.value
Jakarta Persistence (JPA) Method in jakarta.persistence.IdClass Class value The primary key class, which must declare fields or properties with names and types that match the Id fields and properties of the annotated entity class. Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.GeneratedValue.strategy
Jakarta Persistence (JPA) Method in jakarta.persistence.GeneratedValue GenerationType strategy (Optional) The primary key generation strategy that the persistence provider must use to generate the annotated entity primary key. Default: AUTO Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.ForeignKey.value
or columns to which the foreign key annotation is applied. ConstraintMode.NO_CONSTRAINT specifies
|
|
jakarta.persistence.NamedEntityGraph.subclassSubgraphs
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedEntityGraph NamedSubgraph[] subclassSubgraphs (Optional) A list of subgraphs that will add additional attributes for subclasses of the annotated entity class to the entity graph. Specified attributes from superclasses are included in
|
|
jakarta.persistence.NamedNativeQueries.value
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedNativeQueries NamedNativeQuery[] value (Required) Array of NamedNativeQuery annotations . Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.NamedEntityGraph.name
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedEntityGraph String name (Optional) The name used to identify the entity graph in calls to EntityManager.getEntityGraph . If no name is explicitly specified, the name defaults to the entity name of the annotated root entity. Entity graph
|
|
jakarta.persistence.NamedEntityGraph.includeAllAttributes
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedEntityGraph boolean includeAllAttributes (Optional) Includes all of the attributes of the annotated entity class as attribute nodes in the NamedEntityGraph without the need to explicitly list them. Included attributes can still be fully
|
|
jakarta.persistence.NamedStoredProcedureQueries.value
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedStoredProcedureQueries NamedStoredProcedureQuery[] value (Required) Array of NamedStoredProcedureQuery annotations . Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.NamedQueries.value
Jakarta Persistence (JPA) Method in jakarta.persistence.NamedQueries NamedQuery[] value (Required) An array of NamedQuery annotations . Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.MapKeyColumn.unique
Jakarta Persistence (JPA) Method in jakarta.persistence.MapKeyColumn boolean unique (Optional) Whether the column is a unique key. This is a shortcut for the UniqueConstraint annotation at the table level and is useful for when the unique key constraint corresponds to only a single column
|
|
problem with lazy loading - unittest project attached
( org.springframework.transaction. annotation .Transactional ) to testAddBars both tests pass. support Support I think that when the test is not annotated with @Transactional - an ad hoc ... with @Transactional annotated methods to add the relationships. i didn't used @Tranactional for test classes
|
|
Mismatch client-server protocol prefix
annotations work. The weird thing is that this works perfectly in any other app ... don't understand it fully. This are the annotations of the config class: @SpringBootApplication ... is the @EnableSpringConfigured annotation . It just doesn't makes sense. In this project we aren't using AspectJ enhanced
|
|
JSON serialization and __odbHidden members
" is also (unwantenly) present with the same value. In general, we can annotate fields to include/exclude them from JSON ... and as google suggest, is annotating needed element with @Xmltransient, but here it doesn't work ... . tester15 John We may support as an option adding an XmlTransient annotation automatically
|
|
EntityManager JPA or JDO impl and different behavior
of with eager fetch annotation and the map values were still lazy loaded(using the latest objectdb 2.3 ... is lazy loaded even though it is annotated as EAGER. test2 in ExampleTest prints the Before ... to trying to persist the map. So I set the annotation on Holder.java at line 92 to have CascadeType
|
|
ObjectDB JDO - foreign key constraints
cascading updates and deletes in JDO? There seems to exist a @ForeignKey annotation in JDO, but it doesn't seem to affect the behaviour of my classes. Also, this annotation does not seem to be present in the online ObjectDB JDO annotation list, so this may not be supported by ObjectDB?  
|
|
The attribute column name (EXCEPTION) is a reserved SQL-99 keyword.
annotation that will map the name of the Java field to another name in the database: @Column(name="exceptionText") private String exception; This annotation has no effect when using ObjectDB.   ... .xml file, which is not part of JPA. Anyway, you only need that annotation for some exceptional
|
|
@Unique added afterward is not taken into account
Hello, I encounter an issue with the @Unique annotation . The annotation was added on a given field itemID (String), important point : the annotation was added afterwards (after objects ... " the @Unique constraint on all object already present in the table, including those made before annotation
|
|
Activation error on Schema change
Hi, Is @OrderBy annotation supported ? When I add this annotation to my entity I get an error, saying that I did not activate my ObjectDB (which I did) : Caused by: com.objectdb.o ... .createEntityManager(EMF.java:176) When I remove this annotation my activated ObjectDB works fine.  
|
|
enumeration table? how to on pure jpa?
test pictureCount 588 ... Is there any JPA annotation that can handle all those easiest way ... there is no field value on Column annotation but i need solution like that on pure JPA if possible. Fastest clear way... I've looked some other annotations but i could not find any solution like this. kadirbasol
|
|
How to Remove records from many to many relationship tables in JPA
. annotations .CascadeType.DELETE_ORPHAN) and i applied that as @ManyToMany(fetch = FetchType.EAGER, cascade = {CascadeType.PERSIST, CascadeType.REMOVE}) @Cascade(org.hibernate. annotations .CascadeType.DELETE ... = CascadeType.ALL) @Cascade(org.hibernate. annotations .CascadeType.DELETE_ORPHAN) private List
|
|
Are indexes implicitly created for relationships?
Do the following annotations @OneToMany @ManyToOne @ManyToMany @OneToOne imply @Index ? Thanks, Carl FastModel Ben Schreiber Actually these annotations (except @ManyToMany ... , because of their overhead (which most users are not aware of). You should use the @Index or @Unique annotations explicitly to set indexes. support Support
|
|
Embedded in JDO metadata not working in objectDB 2.x ?
" attribute in the package.jdo XML ? If yes, how to handle this ? 3. Should the @Embedded annotations work ... equivalent to the @EmbeddedOnly JDO annotation ? Questions 1 and 4 (especially) are still valid ... JDO annotation ? Yes. 1. Is the enormous increase of database file size caused by the number
|
|
ObjectDB License Error I got
.manage.config; import org.springframework.context. annotation .Bean; import org.springframework.context. annotation .Configuration; import org.springframework.data.jpa.repository.config.EnableJpaRepositories ... .LocalContainerEntityManagerFactoryBean; import org.springframework.transaction. annotation
|
|
@MappedSuperclass and @Transient not working as I expected
; But here is the problem: The base class of my entity hierarchy is annotated as @MappedSuperclass, and one of its fields is annotated @Transient. I expected that when I persist a subclass, no table ... for classes annotated @MappedSuperclass also merely stored schemas, without the data? (I
|
|
Query filter comparing Dates
removed the @Temporal(TemporalType.DATE) annotation ... . So it seems to me that the @Temporal(TemporalType.DATE) annotation ... . If used, the @Tempora l annotation must indicate which of the three specific types above to use
|
|
Unexpected exception (Error 990) com.objectdb.o.InternalException
(PatternApplicationServiceImpl.java:1) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base_transactions_ annotations _TransactionAspect$1$adc4043cproceed(TransactionAspect.aj:90) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base
|
|
JDO PersistenceManager.getSequence() returns null sometimes
When using JDO without annotations , database sequences are normally defined in the ORM file ... can be declared in classes using JDO annotations . Please try build 2.4.7_05 that should fix the naming issue. support Support I haven't used the JDO Sequence annotation myself, but I believe
|
|
[ObjectDB 2.6.0_04] Unexpected exception (Error 990) com.objectdb.jpa.JpaQuery.getResultList
.run(TargetLinkXmlBypassHandler.java:1) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base_transactions_ annotations _TransactionAspect$1$adc4043cproceed(TransactionAspect.aj:90) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep
|
|
Unexpected not reproducable exception in a query
$AjcClosure3.run(ProfilePreferencesAccess.java:1) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base_transactions_ annotations _TransactionAspect$1$344042f2proceed(TransactionAspect.aj:86) at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com
|
|
error 990 ?
.Method.invoke(Unknown Source) at org.springframework.web.bind. annotation .support.HandlerMethodInvoker.doInvokeMethod(HandlerMethodInvoker.java:710) at org.springframework.web.bind. annotation .support ... .servlet.mvc. annotation .AnnotationMethodHandlerAdapter.invokeHandlerMethod
|
|
InternalException during EntityManager.find()
(ExpressionRepositoryImpl.java:1) ~[na:na] at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base_transactions_ annotations _TransactionAspect$1$344042f2proceed(TransactionAspect.aj:86) ~[na:na] at com.btc.ep.base.transactions. annotations .TransactionAspect.ajc$around$com_btc_ep_base
|