About change

191-200 of 200Refresh
JPA Doc
2

javax.persistence.PessimisticLockException

with this Throwable. The specified array is copied by this call; changes in the specified array
Forum
2

Dependency from enhanced classes to the objectDB library

how we must change the ContextClassLoader that is works. All our experiments have failed. We have create ... /lib) must be added to the target platform. The use of the example has not changed (see post #5 ... .it” as Junit Plug-in Test. In addition to switching to a new ObjectDB version the following changes
Issue
2

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

from findElements. @Stateful // Change 1 - EXTENDED requires a Stateful session bean public class TestQuery {     @PersistenceContext(type=PersistenceContextType.EXTENDED) // change 2 ... change hundreds or even thousands of lists to FetchType.EAGER as a workaround just to perform
Forum
2

Automatic schema evolution causes ArrayOutOfBoundsException

Entity - String name - String iata Now I changed the List to Listchanges produce ... changes: Changing the type of the permissions field from List to List. Changing
Forum
2

Beginners questions

transient boolean changed=false; public boolean isChanged(){ return changed; } public void setChanged(boolean changed){ this.changed = changed; } ...as you can see, I tried to manage changes inside ... such changes (maybe automatically?). Please consider that I cannot use Spring or similar, because the test
Issue
1

combined index not used

that has to be used) may be more stable and less affected by small changes in the query or in ObjectDB. The Explorer includes changes that can help in examining different query plans and selecting ... of query plans by using additional statistic information. To benefit from these changes ObjectDB
Issue
1

InternalException

is possible as a result of schema change, in which id fields are removed. Notice that changing the primary ... change do you mean changing the code for the entity objects and using it against an existing ... occurred mid-run so there is no opportunity for code change. I've also found the following error in
Forum
1

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

the change, close ObjectDB's connection, and run the project again. Important: do all that until a new ... to reproduce a similar situation by changing the order of the values in the enum, i.e. by first using enum ... ). Please try to remember if you might have changed your enum, and also try your test with a clean odb
Issue
1

queries under 2.7.6_4 significantly slower than under 2.7.6

. is there a possibility to switch of the new feature ? There are several changes since version 2.7.6 ... . Still working on your report, hopefully will be able to update soon. Update: The change in ... off this ne behaviour It is easy to add a system property to disable the change in version 2.7.6_01, as
Forum
1

schema update procedure

that it takes several restarts of the the server to complete the change. The issue is that there may be changes in many places. Each change appears to be applied as the class is first encountered ... and everything is fine until the next set of changes are encountered. This cycle may repeat several times