Home » Search

About change

191-200 of 200Refresh
Issue
1

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
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
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
Forum
1

alter table

... This is automatic - just change your class (see Database Schema Evolution in the manual ... indexes are automatically built and activated in the background. so, your strategy is changing ... definition and rebuild the database using the Object Doctor  I'm not sure after index changing
Forum
1

Database Inconsistency or corruption

...), REVISION:=1, isPersisted:=true ... As you can see, I changed from "ProfileName 99" to "ProfileName ... the changes, the Id of the new Value entity was still nulll (See #1). How can this be ? It is true ... the changes, the Id of the new Value entity was still nulll This is normal. You can choose an ID
Issue
1

JQL-Update Queries fails with activated L2-Cache

and fetching Entities afterwards from database. Expected result: Getting changed Entities from database - Actual result: No changes are visble. Scenario 2: Disabled L2 Cache, updating elements using ... result: Getting changed Entities from database - Actual result: Everything ok, but it is quite
Forum
1

lockfiles in client/server mode

)   have i misconfigured something? edit: i should note that changing temp= in /etc/objectdb/objectdb ... using the same directory for their temporary files. Changing the temporary directory path ... ). A better solution could be changing the permissions of the temporary directory (/tmp/ObjectDB) in a way
Forum
1

Merge Issue: Attempt to reuse an existing primary key value

we can confirm that a change in the behavior of merge in build 2.4.6_17 affects your test case. The change was applied following a support ticket that demonstrated a strange merge behavior. Following ... the cascading merge, and then also stored as a third instance during commit as part of the change in
Forum
1

ODB IndexActivation NullPointerException

are built in the background starting version 2.6.6, and apparently the last related code change was in ... schema change or any other hint? Small update: We think a workarround (but not usefull) is to create ... ");     } } If we open a database without any Metamodel changes we don't get the tread. I think