I created a small test project in Eclipse (v 3.4.1) which I attempt to
deploy to a Geronimo (v 2.1.3) server, with the default OpenJPA 1.0.3
installed, running under OS X 10.5.5. There's only one entity class,
learn.eclipse.Person.
Using the first persistence-unit definition in my
Hi
In debugging a transaction related issue, I discovered the following
scenarios and just wanted to verify that these are indeed bugs:
Scenario 1
---
My setup is as follows:
Glassfish v2 with MySQL connection pool called jdbc/SmileDB with
property RelaxAutoCommit=true
I am using local transactions and get this error when executing a NativeQuery
(query.executeUpdate)
openjpa-1.0.1-r420667:592145 nonfatal user error
org.apache.openjpa.persistence.InvalidStateException: Cannot perform an
update or delete operation on select query: Update FPA2.NW_OR_004_14702765
Hi Paul,
The RelaxAutoCommit option appears to only allow transactional methods
to be called if a connection is not transactional. From what I read,
it does not change the auto-commit value. By default, auto-commit is
true for a connection per the JDBC spec. I could have missed
something, but
Hi Fernando,
The snapshot repository was lost when we moved to a different machine for
nightly builds (you can see that the snapshots haven't been updated since
August). I'll work on getting them published in subsequent builds. If you
have a JIRA account would you mind opening an issue [1] ? If
of course I have an account :)
https://issues.apache.org/jira/browse/OPENJPA-753
Michael Dick wrote:
Hi Fernando,
The snapshot repository was lost when we moved to a different machine for
nightly builds (you can see that the snapshots haven't been updated since
August). I'll work on getting
Hi,
I could not reproduce this problem against DB2. Which database are you
using? also,can you post your persistence.xml to see if there is any special
setting?
Fay
--- On Mon, 10/27/08, sbedoll [EMAIL PROTECTED] wrote:
From: sbedoll [EMAIL PROTECTED]
Subject: Native Query: Update fails
Hi Doug,
By setting openjpa.jdbc.SynchronizeMappings property to the value
you've specified, the schema should be created for you. You could try
enabling OpenJPA trace to see if there are any messages in the log
that may show whether there was a problem during the the schema
creation process.
Fay Wang wrote:
Hi,
I could not reproduce this problem against DB2. Which database are you
using? also,can you post your persistence.xml to see if there is any
special setting?
Fay
--- On Mon, 10/27/08, sbedoll [EMAIL PROTECTED] wrote:
From: sbedoll [EMAIL PROTECTED]
Subject:
