Re: Exception of merge method.

Hi Yu, This is not expected behavior. You should be able to detach and merge your entity into a new persistence context. The error you're getting is because you have a value specified in a GeneratedField (ie in your entity you have @GeneratedValue on the field). The field in question is

Re: FW: Memory leak

Hi David, There have been a few changes in PersistenceProviderImpl. One was to make the non-finalizing BrokerImpl the default (must be overridden in your config) another that might be interesting was adding a pool of EntityManagerFactories. From what I've seen the EMF pool is not used by

openJPA generates select per row - impossible to use for select statements

Hi! I'm new with openJPA, and didn't manage to get over the problem with simple select statement for one object after a few days of investigation. Please help! For simple select from one object, OpenJPA ( same strategy for 1.0, 1.2.1, 2.0 ) fist generates right query to retrieve all fields, and

Re: Named Query fails but SQL works

I find out more. It is not open jpa problem. It looks like jpatemplate. This works: getJpaTemplate().find(SELECT new Organization(o.orgId, o.orgName) FROM Organization o where o.custOrgId='+custOrgId+' and o.ooid='+ooid+' and o.sor='+sor+'); I was using: @NamedQuery (

Re: Schema generation with unique constraints

Prashant Bhat wrote: Yes, but I think it's fixed only in the trunk and changes are not merged into 1.3.x branch. Or am I missing something here? I'd like to continue using OpenJPA-1.x for our upcoming release without updating to the OpenJPA-2.0-snapshots. I can verify that this problem

Re: openJPA generates select per row - impossible to use for select statements

Hi Mikhail V. Ostryanin. The code you show is not sufficient to generate the log output. What happens after you get the result list? What code actually generates the individual select calls? Regards, Craig On Jul 14, 2009, at 7:07 AM, Ostryanin, Mikhail wrote: Hi! I’m new with openJPA,

Re: Named Query fails but SQL works

Ahhh... I don't remember you indicating that you were using Spring... :-) Using wrappers like getJpaTemplate() around the JPA invocations can introduce some anomalies... I would still be interested in understanding the issue after you touch base with Spring. For the most part, getJpaTemplate

Re: Named Query fails but SQL works

The other thing I found is that the code: getJpaTemplate().find(SELECT new Organization(o.orgId, o.orgName) FROM Organization o where o.custOrgId='+custOrgId+' and o.ooid='+ooid+' and o.sor='+sor+'); Only works for hibernate. Looks like openjpa turns this find operation back to a sql with

Re: Schema generation with unique constraints

ljnelson wrote: I can verify that this problem still exists in the 1.3 branch and running, at least, on the H2 database. What would it take to get this merge to happen? I can also narrow down the bug's scope somewhat in case that helps (or perhaps it has truly been fixed elsewhere?).

Re: Exception of merge method.

Hi mike, Yes, id field with @GeneratedValue(strategy=GenerationType.AUTO) annotation is the primary key field and I didn't serialize the entity. I just modified some fields of the entity in the same VM and try to merge the entity into a new context. Regards, Yu Wang On Tue, Jul 14, 2009 at 9:38