ObjectDB Database Search

Hi, for cascading persist, I have 3 choices: - Either locally (@OneToOne(cascade=CascadeType.PERSIST)) - Either at objectdb level ( ) - Either at JPA global level ( orm .xml).   For defining fetch policy, I know the local way to do it (@ManyToOne(fetch=FetchType.LAZY)). Is there any way

Adam There is no reason for you to be surprised. Asking for advice about ORM problems in an object

, but seems to be tied somehow into the Hibernate ORM . My question is: Does anybody use the "JPA

Hi, could someone recommend a good tool to use for data migration from SQLServer to ObjectDB. irene05 irene lan Unfortunately there is currently no such automatic tool. Using a JPA ORM library (e.g. Hibernate or EclipseLink) you can write your own conversion program that retrieves data from

. Could you explain how can I fix this problem? Harman Alexander Golyshkin ORM /SQL annotations are silently ignored

applications that use an ORM -based JPA provider (such as Hibernate, TopLink, EclipseLink, OpenJPA, JPOX

Here is the description of the problem we are facing:
We have an entity DialogActionNew which previously was located in ObjectDB and recently has been transferred to PostreSQL. We are using ORM Hibernate
When getting this entity from PostgreSQL with the key EntityManager.find(id), we receive

:597) at org.springframework. orm .jpa.SharedEntityManagerCreator$DeferredQueryInvocationHandler.invoke

) is not supported by ORM JPA implementations, so you will be leveraging the performance advantage of ObjectDB. support Support

.springframework. orm .jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke

Hi All, For some reason I'm not able to make the @OrderColumn annotation work. The test case is attached to the thread. Kind regards Martin1978 Martin Mihalev As stated on this documentation page,  this ORM /SQL annotation is silently ignored by ObjectDB. This is because ObjectDB does not map

.springframework. orm .jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke

Added support of JPA 2.1 persistence.xml and orm .xml formats. Added implementation of equals to JPA Metamodel attributes. Fixed ObjectDB OSGi bundle to support enhanced classes. Fixed handling class loader switch (avoiding automatic database close and reopen). Fixed a NullPointerException

.springframework. orm .jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke

If i annotate a getter with: @Column(unique = true) it's simply ignored. If i use @Unique it works perfectly. mosi0815 Ralph Moser Usually ObjectDB silently ignores ORM annotations. This is not a bug (it is  documented ). However, since this may make switching from other JPA implementations

). Added support of @Column(unique="true") and equivalent ORM XML ( issue #550 ). Fixed @PrePersist

getOwner() { return owner; } (For completeness I've left the old ORM annotations in

that would make it inadequate to do what I want, I just see it as an ORM tool used to awkwardly map