Hi,
JPA makes me mad these days ;-) I have a simple DAO which might produce invalid
JPAQL.
@Repository
@Transactional
public class MetaDataDaoImpl implements MetaDataDao {
public Object getClientMetaDataByObjName(String objname, long client) {
Query query = em.createQuery("select x from
Hi,
i found out that some one-to-one relations in the Superclass added some heavy
performance penalties. I ve not seen it in the SQL logs though. Perhaps i
missed it.
Cant comment on the detachment. It seems that its not the problem at all in my
case.
---
regards
Marc Logemann
http://www.logem
Hi, Experts,
I am having an issue with detached object in OpenJPA.
Setter method of relationship field does not work.
Setter method of primitive field works fine.
Here is an example
===
...
Foo foo = entityManager.find(Foo.class, 1);
Bar foo = entityManage
> -Original Message-
> From: Kevin Sutter [mailto:kwsut...@gmail.com]
> Sent: Thursday, December 03, 2009 11:27 AM
> To: users@openjpa.apache.org
> Subject: Re: What happens with invalid query hints?
>
> Yep, I think we're all in agreement on how we should process these
> hints.
> But, the
Yep, I think we're all in agreement on how we should process these hints.
But, the point of the original posting was that the documentation doesn't
explain this very well. So, we still need a JIRA to get this cleaned up.
Agree?
Kevin
On Thu, Dec 3, 2009 at 12:25 PM, Pinaki Poddar wrote:
>
> Cr
Craig is right.
OpenJPA categories a hint key in the following categories (from JavaDoc on
HintHandler)
* 1. Supported: A key is known to this receiver as collected from
different
* parts of the system. The value of a supported key is recorded and
* available via {...@link #getHints
When you call cc.merge(ooo); any changes made to that instance while it was
detached will be persisted to the DB.
I assume your comment "Here I modify the ooo but I want this modif to be
persist, not the other one before" means that you only want the changes from
after the tran begins to be persis
Hi the list,
Am i right on the following pseudo code ?
// Note the detach.
// getFullById come back with an instance of MyObject from the
primary key
final MyObject ooo = detach(getFullById(cc
< Here I modify (a lot) ooo but don't wan't the mo
Marc -
In the case where you call em.find(...) and it takes 500ms how long does
that operation take if the result doesn't need to be detached? The reason I
ask is that I've been doing some performance work and we found that in some
instances we are spending way too much time detaching Entities.
-
I'm not on the Mojo list, so I'm not sure what they're saying there, but I do
know from their JIRA that there are only 2 issues in the way of a release and
one of them is relatively trivial
http://jira.codehaus.org/browse/MOPENJPA-3
You could vote for it I guess.
The other issue is something
small correction :
public class SomeDao {
@SuppressWarnings("unchecked")
public Object getMetaData(Class clazz, long oid) {
Object o = em.find(clazz, oid);
return o;
}
..
}
CALLER:
Object o = someDao.getMetaData(Foo.class, 1);
---
regards
Marc Logemann
http://www.logem
Hi,
i am facing some weird performance issues. Given this JPA Query:
public class SomeDao {
@SuppressWarnings("unchecked")
public Object getMetaData(Foo.class, long oid) {
Object o = em.find(clazz, client);
return o;
}
..
}
@Entity
@VersionColumn(name = "jpaversion"
Hello Mojoers, I support the request for an e.g. non-SNAPSHOT v1.1
OpenJPA Maven plugin published to a repo somewhere...
Would be nice to be able to use the
http://jira.codehaus.org/browse/MOPENJPA-8 fix!
-Original Message-
From: Adam Hardy [mailto:adam@cyberspaceroad.com]
Sent: We
13 matches
Mail list logo
