, 2007 2:50 PM
To: open-jpa-commits@incubator.apache.org
Subject: svn commit: r510281 - in /incubator/openjpa/trunk:
openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/
openjpa-kernel/src/main/java/org/apache/openjpa/kernel/
openjpa-persistence/src/main/java/org/apache/openjpa
commit: r510281 - in /incubator/openjpa/trunk:
openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/
openjpa-kernel/src/main/java/org/apache/openjpa/kernel/
openjpa-persistence/src/main/java/org/apache/openjpa/persistence/
Author: wisneskid
Date: Wed Feb 21 14:50:04 2007
New
What's the word on this issue?
Last record I have is:
Okay, I think we need to back out these last two changes and revert
back to
revision 509885. Dave needs to go back to the drawing board for
this db2
optimization change, probably create a JIRA report for this proposed
change, and use
I have backed out the original changes via svn revision 512327 -- just did
it this morning. Dave will create a JIRA report for this optimization so
that we can work through the issues and then we'll integrate a new set of
changes.
Kevin
On 2/22/07, Abe White [EMAIL PROTECTED] wrote:
3.
3. OpenJPA does support a means of passing Oracle hints along
through to
the DBDictionary. Should we be trying to reuse some of the
capabilities
here?
+1
4. In the following snippets, I'd rather if we used 'Integer.valueOf
(1)'
or, better yet, a symbolic constant, instead of creating new
: Wednesday, February 21, 2007 2:50 PM
To: open-jpa-commits@incubator.apache.org
Subject: svn commit: r510281 - in /incubator/openjpa/trunk:
openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/
openjpa-kernel/src/main/java/org/apache/openjpa/kernel/
openjpa-persistence/src/main/java/org/apache
