Hi William,
I have been running OpenJPA against DB2 v9 with no major issues, and I
believe others on the forums have been doing so as well. Admittedly this
isn't a certification, but it's at least anecdotal evidence that DB2 v9 will
work.
For KODO I'd have to refer you to BEA's support
OK, now that I found the relevant section in the documentation I understand
what William is asking for.
What level of testing do we need to do before we can add a new version of
DB2 to the list of supported databases? Is just running our unit test bucket
sufficient to add a new database to the
Hi list,
AFAIK, the latest DB2 version is DB2 enterprise server edition V9.1. But but
current OpenJDK only supports DB2 UDB v8.1. Do we have any plans to certify DB2
UDB V8.2 and DB2 v9 recently? Or more realistically -- are there any cases to
run OpenJPA/KODO on DB2 UDB v8.2 or DB2 v9?
Any
What level of testing do we need to do before we can add a new
version of
DB2 to the list of supported databases? Is just running our unit
test bucket
sufficient to add a new database to the list or do we need a more
formal
process?
That's a very good question, and one that I don't
[
https://issues.apache.org/jira/browse/OPENJPA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ezzio updated OPENJPA-236:
Issue Type: New Feature (was: Bug)
In fact, there is no way to override the insertion SQL being
Hi Abe,
I got a chuckle out of your solution, which, in a long tradition of good
engineering, changes the problem.
Unfortunately, customers are not always open to suggestions about how
their requirements can be modified. So, I've changed the bug report to
a feature request, as it appears the
Have you confirmed with the customer that they must have one-sided
relations? It's possible that they won't really mind having extra
backpointers in their model.
-Patrick
On 5/9/07, David Ezzio [EMAIL PROTECTED] wrote:
Hi Abe,
I got a chuckle out of your solution, which, in a long tradition
[
https://issues.apache.org/jira/browse/OPENJPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494583
]
Marc Prud'hommeaux commented on OPENJPA-51:
---
This patch caused 17 TCK tests to start failing, so it needs
[DISCUSS 1]:
Many database systems now have support for XML types which includes DB2 v9.1,
DB2 zOS v9, Oracle 10g, and SQLServer 2005.
Tables may contain XML columns where you can store XML documents.
What is OpenJPA's position of supporting the XML columns ?
The current mapping choices for XML
[
https://issues.apache.org/jira/browse/OPENJPA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-194.
Resolution: Fixed
Committed patch. The binary artifact will be named
With 5 +1 votes and no -1 or 0 votes, the proposal passes. I've gone
ahead and committed the patch for OPENJPA-194.
Note that I only changed the artifact names, not the directory names
in which they reside. We can always start another vote on shuffling
around the directory names if
Note that I only changed the artifact names, not the directory names
in which they reside. We can always start another vote on shuffling
around the directory names if people deem it a worthwhile endeavor.
I think that we should make the change, for the sake of reducing
future confusion. But we
+1 Thanks Marc.
On 5/9/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Sounds good to me.
On May 9, 2007, at 3:28 PM, Patrick Linskey wrote:
Note that I only changed the artifact names, not the directory names
in which they reside. We can always start another vote on shuffling
around
On May 9, 2007, at 6:09 AM, Michael Dick wrote:
OK, now that I found the relevant section in the documentation I
understand
what William is asking for.
What level of testing do we need to do before we can add a new
version of
DB2 to the list of supported databases? Is just running our
I have 2 objects related, when I create both in a transaction and set one
object on another and then committing. I get this error. The objects are
stored in DB2 with auto increment -ing identity.
This error can also occur when a horizontally or vertically mapped
classes uses auto-increment
15 matches
Mail list logo
