Hello!
Neither of those, I just execute the program twice. So, it's not about
the managed / detached entities.
Fay Wang wrote:
The em.merge will return the merged entity.
EntityA mergedEntity = em.merge(newEntity);
During your second merge call, did you call
em.merge(mergedEntity)
Hi Kevin
Thanks for the information, I have added the following value to my
persistence.xml file:
property name=openjpa.jdbc.DBDictionary
value=hsql(useSchemaName=true)/
This will generate tables in the specified schema as expected.
I still think that this option should be true by default. If
So I'm pretty new to using OpenJPA so this might be a simple fix...
I'm doing the following query.
select new com.bcbst.odstats.ejb.beans.RangeStats(count(a), avg(a.loadTime))
FROM ODUsage a
WHERE
a.accessDate BETWEEN :startDate AND :endDate and
a.loadTime is not NULL
I've noticed the
This is a bug in openjpa. JIRA-1371 is open to address this problem.
- Original Message
From: Constantine Kulak c...@mail.by
To: users@openjpa.apache.org
Sent: Fri, October 30, 2009 12:54:19 AM
Subject: Re: Insert is called instead of Update when merge() with complex IDs
Hello!
Hi,
JPQL implementation of OpenJPA 1.3 (or before) had this limitation: if you
specify a NEW in select projection then rest of the projection clauses are
silently ignore.
This is in agreement with your observation.
The good news is, the latest version of OpenJPA does not have any such
