InvalidStateException

Hi, I changed my persistence.xml to comment out Synchronization !-- property name=openjpa.jdbc.SynchronizeMappings value=buildSchema(ForeignKeys=true)/ -- Then I started getting following error R Caused by: 4|false|0.9.6-incubating-SNAPSHOT

JDBC SAvepointManager does not work

I have defined JDBC SavepointManager in my persistence.xml.I am running against DB2 v9 property name=openjpa.SavepointManager value=jdbc/ Now a run a test client as follows EntityManagerFactory emf = Persistence. * createEntityManagerFactory* (dwtest); EntityManager em =

Re: JDBC SAvepointManager does not work

you were right by setting Savepoint after some persistence operation seems to fix the problem thanks ritika On 1/16/07, Abe White [EMAIL PROTECTED] wrote: Try performing a persistence operation (persisting an entity, changing a persistent entity, deleting an entity, etc) before setting the

openjpa logging

I am running a Query select d.breed from Dog d .This query gives an argument exception because Dog does not have a field called breed.Now there is no way I can make openjpa log this exception.The only way I can see this exception is by having a try and catch block in my code and catching and

Exception in thread main 4|false|0.0.0 org.apache.openjpa.persistence.InvalidStateException: You cannot transfer large result set fields from one object or field to another.

Hi, I have orderline defined as LRS in Orders.In persistence.xml I have this defined property name=openjpa.FetchBatchSize value=1 / My test program gives the above error em.getTransaction().begin(); Query query = em.createQuery(select object(o)from Orders o where o.o_id=3001 and

Re: svn commit: r525252 - in /incubator/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql: AbstractDB2Dictionary.java DB2Dictionary.java

yes will do that ritika On 4/3/07, Craig L Russell [EMAIL PROTECTED] wrote: Hi David, The DB2Dictionary class doesn't compile with 1.4 due to autoboxing. Can you please fix this? Craig public String getForUpdateClause(JDBCFetchConfiguration fetch, boolean forUpdate) { String

Re: [jira] Commented: (OPENJPA-168) sql optimize n rows query hint

It has not been documented in the OPENJPA documentation. On 4/4/07, Patrick Linskey (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486820] Patrick Linskey commented on

Re: [jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

Message- From: Ritika Maheshwari [mailto:[EMAIL PROTECTED] Sent: Thursday, April 05, 2007 1:18 PM To: open-jpa-dev@incubator.apache.org Subject: Re: [jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS Informix has the following SET TRANSACTION

Re: svn commit: r526212 - in /incubator/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc: kernel/JDBCFetchConfigurationImpl.java sql/DBDictionary.java

Patrick, With your recent changes regarding the OPENJPA-182 The logic has changed a little.What was intended was that if the forUpdate flag = true we append the FOR UPDATE CLAUSE.But in case of DB2 if the forUpdate flag = false then we append FOR READ ONLY clause.Now the FOR READ ONLY

Re: svn commit: r526212 - in /incubator/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc: kernel/JDBCFetchConfigurationImpl.java sql/DBDictionary.java

of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. -Original Message- From: Ritika Maheshwari [mailto:[EMAIL PROTECTED] Sent: Friday, April 06, 2007 10:14 AM

Re: svn commit: r526212 - in /incubator/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc: kernel/JDBCFetchConfigurationImpl.java sql/DBDictionary.java

for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. -Original Message- From: Ritika Maheshwari [mailto:[EMAIL PROTECTED] Sent: Friday, April 06

Re: svn commit: r526212 - in /incubator/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc: kernel/JDBCFetchConfigurationImpl.java sql/DBDictionary.java

and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. -Original Message- From: Ritika Maheshwari

Re: OPENJPA-182: reuse Connection constants or create our own?

Patrick, we just discovered that there is a problem with this fix.Theproblem is that the FOR READ ONLY flag is getting generated for subselects as well. Basically for DB2 if forUpdate was false we append FOR READ ONLY we need another check to see that it is not a subselect.To me it

Re: [jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

1. OK I think I will open a new issue for the bug 2. I will redo the formatting 3.To be able to use DBDictionary method we will have to change the signature of the toSelect(SQLBuffer selects, JDBCFetchConfiguration fetch,SQLBuffer from, SQLBuffer where, SQLBuffer group,SQLBuffer having,

[jira] Created: (OPENJPA-172) DSRA9250E: Operation setTransactionIsolation is not allowed during a global transaction for Shareable Connections.

://issues.apache.org/jira/browse/OPENJPA-172 Project: OpenJPA Issue Type: Bug Components: jpa Affects Versions: 0.9.6 Environment: Websphere 6.1 for zos and DB2 zos V8 Reporter: Ritika Maheshwari Fix For: 0.9.6 My persistence.xml

[jira] Updated: (OPENJPA-168) sql optimize n rows query hint

[ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritika Maheshwari updated OPENJPA-168: -- Attachment: OPENJPA-168.patch2.txt sql optimize n rows query hint

[jira] Commented: (OPENJPA-168) sql optimize n rows query hint

[ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483203 ] Ritika Maheshwari commented on OPENJPA-168: --- In the singleResult method of the kernel QueryImpl when null

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritika Maheshwari updated OPENJPA-182: -- Attachment: openJPA182.patch here is a patch for this feature db2 update lock

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ritika Maheshwari updated OPENJPA-182: -- Attachment: JIRA182-subselect.patch we just discovered that there is a problem

[jira] Created: (OPENJPA-222) FOR READ ONLY clause getting generated for subselects

Affects Versions: 0.9.7 Reporter: Ritika Maheshwari FOR READ ONLY clause is generated for subselects in DB2. which throws a DB2 Exception -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.