Hi Craig,
I checked in the setUp changes (revision 357680). I used another JDO
issue number JDO-147 in the commit message, because the cleanUp changes
are not directly related to the float issue.
Please note, with the setUp changes the first run of one of the
operators test I changed might
Jörg von Frantzius wrote:
After having thought about it for a while, I started to doubt whether
we really need a recursion-depth number here. Can you think of a
case where you'd need any value greater than 1 here?
We have a case in which we need a recursion-depth greater than 1:
We use a
Marco Schulze wrote:
Jörg von Frantzius wrote:
After having thought about it for a while, I started to doubt whether
we really need a recursion-depth number here. Can you think of a
case where you'd need any value greater than 1 here?
We have a case in which we need a recursion-depth greater
Allowing multiple levels of a tree structure to be pre-fetched would allow
more efficient traversal of the tree structure than simply iterating one
level at a time. The implementation could use relational vendor specific
features, I know Oracle supports such recursive traversals.
David Jordan
Michelle Caisse wrote:
Hi Jean,
The checklist is useful. It would be nice to have information about who
needs to perform each task, by karma category.
Thanks for the suggestion and please let me know about any other
confusions -- or even post to the
Hello,
if I'm not misteaken, it currently is not possible to have checking of
NOT NULL constraints be deferred to commit-time. It's possible to have
FK and unique constraints checking deferred, but not NOT NULL constraints.
NOT NULL constraints can result from primitive types being used, or
Javadogs,See JIRA issue JDO-243 http://issues.apache.org/jira/browse/JDO-243?page=allOrdering should have the same restrictions as for the Select clause. That is, if grouping is used, only expressions in the Grouping clause and aggregate expressions can be in the Ordering clause.The JDO
[ http://issues.apache.org/jira/browse/JDO-262?page=all ]
Michelle Caisse closed JDO-262:
---
Resolution: Fixed
Fixed in revision 357570
Add element-type metadata to ArrayCollections
-
Key:
TestArrayCollections: Field
org.apache.jdo.tck.pc.fieldtypes.ArrayCollections.ArrayOfObject1 is declared
as a reference type (interface/Object) but no implementation classes of
java.lang.Object have been found!
[ http://issues.apache.org/jira/browse/JDO-206?page=all ]
Michael Bouschen updated JDO-206:
-
Attachment: JDO-206.patch2
Attached you find a new patch (JDO-206.patch2) for review.
The patch changes the schema for derby and uses the coumn type REAL for
I'm happy to announce that Apache JDO http://db.apache.org/jdo, which has been in incubation for the past 7 months, has graduated from the Apache Incubator and is now an ongoing sub-project of the Database (DB) Top Level Project at Apache. http://db.apache.org It joins Apache Derby, DdlUtils,
[
http://issues.apache.org/jira/browse/JDO-206?page=comments#action_12360881 ]
Craig Russell commented on JDO-206:
---
The change looks good.
This sure had me puzzled for quite a while. The root cause of the issue was
that the float values in the class
[
http://issues.apache.org/jira/browse/JDO-241?page=comments#action_12360883 ]
Craig Russell commented on JDO-241:
---
The patch looks good.
JPOX returns wrong query result for non-extent queries.
---
13 matches
Mail list logo
