[jira] Resolved: (OPENJPA-1876) Slow JDBC tests

[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milosz Tylenda resolved OPENJPA-1876. - Resolution: Fixed Fix Version/s: 2.2.0 > Slow JDBC tests > --- > >

Re: Oracle nvarchar2 null value

I agree. This is a good candidate for improvement, could you open a JIRA issue for the problem? -mike 2011/1/24 Vetal > Trying to persist object to Oracle with null value at nvarchar2 type > column causes > > Caused by: > org

[jira] Updated: (OPENJPA-1912) enhancer generates invalid code if fetch-groups is activated

[ https://issues.apache.org/jira/browse/OPENJPA-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-1912: --- Attachment: OPENJPA-1912-test.patch This unit test demontstrates the problem. I get the fol

Oracle nvarchar2 null value

Trying to persist object to Oracle with null value at nvarchar2 type column causes Caused by: org.apache.openjpa.persistence.PersistenceException: недействительный шаблон имени: CHES.NVARCHAR2 FailedObject: prepstmnt 1108543980 INSERT INTO CHES.BAL_ENET_DATA (ID, GUID, NAME, IS_SUBS

Re: way to restore the DetachedStateManager on deserialisation?

Nope, it just writes all the fields (including any parent fields) Currently tinker a unit test especially for you ;) LieGrue, strub --- On Mon, 1/24/11, Rick Curtis wrote: > From: Rick Curtis > Subject: Re: way to restore the DetachedStateManager on deserialisation? > To: dev@openjpa.apache.o

Re: way to restore the DetachedStateManager on deserialisation?

> My goal is to somehow generate super.readExternal() and super.writeExternal() to subsequently process the parent class. Does this make sense to you? Yes, this sounds reasonable. I'm quite surprised that isn't how we work today. On Mon, Jan 24, 2011 at 7:38 AM, Mark Struberg wrote: > Yes, this

Re: way to restore the DetachedStateManager on deserialisation?

Yes, this is a workaround I figured already. But the downside is that we need to tweak a lot of classes and it is really a bug imo. It's not a showstopper, but it's a bug ;) See OPENJPA-1912. I'm currently writing a unit test in the openjpa-persistence-jdbc test package org.apache.openjpa.enha

Re: way to restore the DetachedStateManager on deserialisation?

What happens if you change your private fields to protected? Thanks, Rick On Jan 24, 2011, at 5:51 AM, Mark Struberg wrote: > Hi! > > I've tried it again and it works (maybe I had a typo in my config, who > knows). > > So I now get the pcStateManager back, but now another issue appears: the

[jira] Commented: (OPENJPA-1912) enhancer generates invalid code if fetch-groups is activated

[ https://issues.apache.org/jira/browse/OPENJPA-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985642#action_12985642 ] Mark Struberg commented on OPENJPA-1912: It seems this has nothing to do with fet

Re: way to restore the DetachedStateManager on deserialisation?

Hi! I've tried it again and it works (maybe I had a typo in my config, who knows). So I now get the pcStateManager back, but now another issue appears: the code uses Externalizable and the generated readExternal and writeExternal try to also write the parent fields. This is bad since it doesn'