[jira] Assigned: (OPENJPA-63) Better pessimistic lock support for DB2 v8.2+

[ http://issues.apache.org/jira/browse/OPENJPA-63?page=all ] Kevin Sutter reassigned OPENJPA-63: --- Assignee: Kevin Sutter Better pessimistic lock support for DB2 v8.2+ - Key: OPENJPA-63

[jira] Resolved: (OPENJPA-63) Better pessimistic lock support for DB2 v8.2+

[ http://issues.apache.org/jira/browse/OPENJPA-63?page=all ] Kevin Sutter resolved OPENJPA-63. - Resolution: Fixed I finally got around to verifying Igor's latest patch. It looks good and tests out okay on my system. Thanks for your patience, Igor.

Re: openjpa NativeQuery and NamedNativeQuery only allow select sql statements

George- Sounds like a bug ... I think you should be allowed to execute an update native query. Can you file a JIRA report at https:// issues.apache.org/jira/browse/OPENJPA with the complete stack trace (including any nested stacks) and the code snippet that executes the query? On Dec

RE: openjpa NativeQuery and NamedNativeQuery only allow select sql statements

Hi, How are you executing the query? I'm guessing that you're using Query.getResultList() or Query.getSingleResult() instead of Query.executeUpdate(). -Patrick -- Patrick Linskey BEA Systems, Inc. ___ Notice: This email

Re: svn commit: r482189 [1/2] - in /incubator/openjpa/trunk: openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/ openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/ openjpa-lib/src/main/java/

If it is due to line endings, in future the files should be marked with eol-style=native. It looks like there are no properties associated with the files in svn. Craig On Dec 4, 2006, at 10:14 AM, Patrick Linskey wrote: I think that it's to do with line endings. No idea how to resolve the

Line endings!

I just wanted to make sure everyone sees this, because I bet many of us don't have our config file set up correctly (I know I didn't): Probably the offender's local svn file settings are wrong and not as recommended at http://www.apache.org/dev/svn-eol-style.txt thanks david jencks

Re: svn commit: r482189 [1/2] - in /incubator/openjpa/trunk: openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/ openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/ openjpa-lib/src/main/java/

As a test, I changed the property svn:eol-style in the two jdbc projects. I used the command cd src/main/java; svn propset -R svn:eol-style native org It went through the files, cleaned them up to a normalized state and the commit messages indicate the files that had different eol

cache-topic for clustered Kodo

Patrick, Your 'cacheTopic' theme effectively replaces the original requirement of having a configuration.getId(), at least for this purpose (I remember that it has other usages e.g. in logging). For ClusterRemoteCommitProvider, i will default cacheTopic value with configuration.getId().