Craig,
I like the idea of putting together a roadmap. I had started this
conversation with Patrick earlier this week, so your timing is perfect.
Concerning the 0.9.7 release... I would like to shut down the development
of this release somewhat soon. We have produced so many CTS-related,
[
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
Schemas defined in orm.xml are only applied when a name is also specified.
---
Key: OPENJPA-179
URL: https://issues.apache.org/jira/browse/OPENJPA-179
Project: OpenJPA
I don't know what behavior to expect out of JDBC drivers outside of a
transaction.
Regarding avoiding transactions: in most situations, you should not see
any significant performance penalties for using transactions with
OpenJPA. The authors of Pro EJB3 are all Oracle employees, so maybe
there is
It's Java EE, i,e, run under the appserver. I'll let you know what is does the
tracing shows.
-marina
Patrick Linskey wrote:
Did you run the OpenJPA enhancer on your classes before running the
test, or, are you running in an environment that should be doing
automatic class processing (such as
Statement.setQueryTimeout() is required to be implemented in order to
achieve compliance with the JDBC specification. I would expect that
current JDBC drivers from the majority of the JDBC driver companies have
implemented this hopefully in a manner that works most of the time.
Marc
Interesting... but after switching back to Derby, it all worked. Let me try and
see if it's the 1st run after 1st deploy that causes any problems.
-marina
Patrick Linskey wrote:
Did you run the OpenJPA enhancer on your classes before running the
test, or, are you running in an environment
Not sure if you use Statement.cancel() at all but this is an optional
method for JDBC and requires a SQLFeatureNotSupportedException to be
thrown if it is not supported (JDBC 4)
Patrick Linskey wrote:
Also, you may be interested in the OpenJPAEntityManager.cancelAll()
method call, which uses
