[
http://issues.apache.org/jira/browse/JDO-445?page=comments#action_12460509 ]
Michael Watzek commented on JDO-445:
Hi Craig,
the patch looks good! Please find my comments below:
- PersistenceManagerProxies are cached using PMF instances
!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
[
http://issues.apache.org/jira/browse/JDO-354?page=comments#action_12372236 ]
Michael Watzek commented on JDO-354:
I noticed that there is a little mismatch between test case MakePersistent, the
.sql files, and the .orm files for mappings 5, 6, 7 wrt
Versions: JDO 2 rc1
Reporter: Michael Watzek
Assigned to: Michael Watzek
Priority: Minor
Fix For: JDO 2 final
I noticed that there is a little mismatch between test case MakePersistent, the
.sql files, and the .orm files for mappings 5, 6, 7 wrt. which persistence
capable
!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
class.
I propose to update the API doc: Creates an instance of a
persistence-capable interface, or of a concrete or abstract class.
Regards,
Michael
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto
[
http://issues.apache.org/jira/browse/JDO-335?page=comments#action_12370194 ]
Michael Watzek commented on JDO-335:
One comment related to the patch checked in:
Does it make sense to call closePMF() in a finally block just to make sure it
is executed
? O, Gasp!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http
[ http://issues.apache.org/jira/browse/JDO-311?page=all ]
Michael Watzek resolved JDO-311:
Resolution: Fixed
The second patch has been checked in (revision 382739).
Inheritance3 : should check if the JDO implementation supports
article.
[July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated to
include all JDO metadata elements and attributes. [not done]
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL
[ http://issues.apache.org/jira/browse/JDO-311?page=all ]
Michael Watzek updated JDO-311:
---
Attachment: JDO-311.patch2
The second patch implements comments 1. and 2. above. Note, that the second
patch makes all calls
!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
[
http://issues.apache.org/jira/browse/JDO-311?page=comments#action_12368108 ]
Michael Watzek commented on JDO-311:
Some inheritance configurations must specify property jdo.tck.requiredOptions
as shown below:
- inheritance1.conf
[ http://issues.apache.org/jira/browse/JDO-311?page=all ]
Michael Watzek updated JDO-311:
---
Attachment: JDO-311.patch
The attached patch fixes this issue.
Some comments:
I moved method isTestToBePerformed() to class JDOTest. Thus, other test classes
http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30
definitions by CONSTRAINT clauses.
Regards,
Michael
Craig L Russell wrote:
FYI, at the Friday JDO TCK conference call, Michelle volunteered to
update the schema with user-decipherable foreign key names.
Craig
On Jan 27, 2006, at 8:56 AM, Michael Watzek wrote:
Hi Andy,
Do you have some
Fix list of teardown classes in company model reader.
-
Key: JDO-285
URL: http://issues.apache.org/jira/browse/JDO-285
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael
[ http://issues.apache.org/jira/browse/JDO-285?page=all ]
Michael Watzek updated JDO-285:
---
Attachment: JDO-285.patch
The attached patch fixes this issue. It contains two changes:
1) It fixes the order of teardown classes,
2) It fixes call getExtent
/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36
(BatchTestRunner.java:95)
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL
] at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:95)
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783
[ http://issues.apache.org/jira/browse/JDO-258?page=all ]
Michael Watzek reassigned JDO-258:
--
Assign To: Michael Watzek
Write tests for new persistent-nontransactional-dirty lifecycle assertions
[ http://issues.apache.org/jira/browse/JDO-273?page=all ]
Michael Watzek reassigned JDO-273:
--
Assign To: Michael Watzek
Create tests for sections 5.5.8 5.5.9, detachment lifecycle
[ http://issues.apache.org/jira/browse/JDO-273?page=all ]
Michael Watzek updated JDO-273:
---
Attachment: JDO-273.patch
The attached patch implements the lifecycle transition tests for JDO-258 and
JDO-273.
The patch extends the existing test class
[
http://issues.apache.org/jira/browse/JDO-258?page=comments#action_12363716 ]
Michael Watzek commented on JDO-258:
The assertions of this issue have been implemented together with the assertions
of JDO-273. The patch has been attached to JDO-273
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
are detached.
= ... and have fields marked as modified are detached-dirty.
Regards,
Michael
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
[ http://issues.apache.org/jira/browse/JDO-230?page=all ]
Michael Watzek resolved JDO-230:
Fix Version: (was: JDO 2 beta)
Resolution: Fixed
The attched patch has been checked in (revision 355479).
Fix order of makePersistent
/jira/browse/JDO-239
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
The test case DeleteQueryElements fails throwing a NPE for the query below. The
test case is expected to thow a JDOUserException. The same test case succeeds
[ http://issues.apache.org/jira/browse/JDO-194?page=all ]
Michael Watzek reopened JDO-194:
Assign To: Erik Bengtson (was: Michael Watzek)
The test cases MixedVariables and VariablesAndFields fail throwing
NoClassDefFoundError. Both test cases
/browse/JDO-240
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
The test case AggregateResult fails throwing the exception below when DISTINCT
is specified inside an aggregate function. The exception is thrown for COUNT,
SUM
JPOX returns wrong query result for non-extent queries.
---
Key: JDO-241
URL: http://issues.apache.org/jira/browse/JDO-241
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned
JPOX returns wrong query result for test case Grouping.
---
Key: JDO-242
URL: http://issues.apache.org/jira/browse/JDO-242
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Test case Grouping fails for the query below. The query is expected to throw a
JDOUserException because field salary is contained in the result clause and not
contained in the group by clause.
14:22:49,328 (main) DEBUG
: Michael Watzek
Assigned to: Erik Bengtson
Test case ResultClassRequirements fails because JPOX generates illegal SQL for
the query below. The query uses result class java.util.Map. The FROM caluse of
the generated SQL is empty.
14:23:04,625 (main) DEBUG [org.apache.jdo.tck] - Executing API
: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Test case ResultExpressions fails for the query below. The query selects values
of a variable which is bound to a collection.
14:23:16,968 (main) DEBUG [org.apache.jdo.tck] - Executing API query: SELECT
project
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Test case ResultExpressions fails for the query below. The query uses
COUNT(variable) in the result clause. The variable is bound to a collection.
14:23:19,437 (main) DEBUG [org.apache.jdo.tck] - Executing API query: SELECT
COUNT
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Test case ResultExpressions fails for the query below. The query uses a +
operator in the result clause.
14:23:26,203 (main) DEBUG [org.apache.jdo.tck] - Executing API query: SELECT
personid + 1 FROM
: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Test case ResultExpressions fails for the query below. The query selects a
field of a parameter in the result clause. The type of the parameter is a pc
class.
14:23:30,734 (main) DEBUG [org.apache.jdo.tck
[ http://issues.apache.org/jira/browse/JDO-254?page=all ]
Michael Watzek updated JDO-254:
---
Attachment: JDO-254.patch
The attached patch fixes this issue.
Fix message when query compilation fails
Key
Inheritance mapping 1 fails for application identity.
-
Key: JDO-255
URL: http://issues.apache.org/jira/browse/JDO-255
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik
[ http://issues.apache.org/jira/browse/JDO-229?page=all ]
Michael Watzek resolved JDO-229:
Resolution: Fixed
The second patch has been checked in (revision 355060).
Class DeleteCallback must not assume managed relationships
[ http://issues.apache.org/jira/browse/JDO-228?page=all ]
Michael Watzek resolved JDO-228:
Resolution: Fixed
The patch has been checked in (revision 355062).
Enhancer error message for org/apache/jdo/tck/pc/mylib/PCClass.jdo
[ http://issues.apache.org/jira/browse/JDO-167?page=all ]
Michael Watzek resolved JDO-167:
Resolution: Fixed
The second patch has been checked in (revision 355126).
Inheritance mapping 2 needs to be changed to support polymorphic
relationships
[ http://issues.apache.org/jira/browse/JDO-230?page=all ]
Michael Watzek updated JDO-230:
---
Attachment: JDO-230.patch
The attched patch fixes this issue.
Fix order of makePersistent() and addTearDownClass() in localSetUp methods
[ http://issues.apache.org/jira/browse/JDO-167?page=all ]
Michael Watzek updated JDO-167:
---
Attachment: JDO-167.patch
The attached patch fixes this issue.
Inheritance mapping 2 needs to be changed to support polymorphic
relationships to Employees
Versions: JDO 2 beta
Reporter: Michael Watzek
Assigned to: Michael Watzek
Priority: Minor
Fix For: JDO 2 beta
The order of calls makePersistent() and addTearDownClass() in localSetUp
methods is significant: addTearDownClass() must be called before
makePersistent(). This ensures
[ http://issues.apache.org/jira/browse/JDO-229?page=all ]
Michael Watzek updated JDO-229:
---
Attachment: JDO-229.patch2
The second patch implements the comments above.
Class DeleteCallback must not assume managed relationships
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
Hi Craig,
Hi,
On Dec 5, 2005, at 7:40 AM, Michael Watzek wrote:
Hi Craig, Andy
I think there is a portability issue with this test case:
The test case assumes that a JDO implementation supports managed
relationships, because it deletes instances which are referenced by
other instances
Class DeleteCallback must not assume managed relationships.
---
Key: JDO-229
URL: http://issues.apache.org/jira/browse/JDO-229
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned
[ http://issues.apache.org/jira/browse/JDO-229?page=all ]
Michael Watzek updated JDO-229:
---
Attachment: JDO-229.patch
The attached patch implements the comments above.
Class DeleteCallback must not assume managed relationships
[ http://issues.apache.org/jira/browse/JDO-228?page=all ]
Michael Watzek updated JDO-228:
---
Attachment: JDO-228.patch
In file PCClass.jdo elements query were misplaced for both, application
identity and datastore identity. They have to be specified before
Hi Craig,
Hi Michael,
Thanks for your analysis. More comments below.
On Dec 5, 2005, at 4:55 AM, Michael Watzek wrote:
Hi Andy,
Inheritance mapping 2 fails. JPOX doesn't
support it, and the mapping isn't consistent. This needs a few
things: UNION join strategy plus generating a sequence
this and what do they assume is
the join table structure ?
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax
!
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
[ http://issues.apache.org/jira/browse/JDO-147?page=all ]
Michael Watzek updated JDO-147:
---
Attachment: JDO-147.patch
The attached patch fixes this issue.
Methods QueryTest.cleanupCompanyModel and QueryTest.cleanupDatabase have been
removed. Instead
[ http://issues.apache.org/jira/browse/JDO-166?page=all ]
Michael Watzek resolved JDO-166:
Resolution: Fixed
The comments above have been incorporated into the second patch. The second
patch has been checked in (Revision 350282).
Implement new
[ http://issues.apache.org/jira/browse/JDO-217?page=all ]
Michael Watzek resolved JDO-217:
Resolution: Fixed
The attached patch has been checked in (Revision 349919).
The expected result in JDO2 query test cases should have the exact runtime
[ http://issues.apache.org/jira/browse/JDO-222?page=all ]
Michael Watzek resolved JDO-222:
Resolution: Fixed
The patch has been checked in. (Revision 349693).
Test case query.sql.CandidateClass should renamed to
query.sql.NoCandidateClass
[ http://issues.apache.org/jira/browse/JDO-223?page=all ]
Michael Watzek resolved JDO-223:
Resolution: Fixed
The patch has been checked in (Revision 349701).
SupportedMapMethods miss queries calling isEmpty() and size
[ http://issues.apache.org/jira/browse/JDO-217?page=all ]
Michael Watzek updated JDO-217:
---
Attachment: JDO-217.patch
The attached patch fixes this issue.
The list of affected classes in this patch is different compared to the list
above because some
[ http://issues.apache.org/jira/browse/JDO-166?page=all ]
Michael Watzek updated JDO-166:
---
Attachment: JDO-166.patch2
The second patch implements the comments above.
Implement new JDO 2 query tests cases concerning deletion by query
[ http://issues.apache.org/jira/browse/JDO-221?page=all ]
Michael Watzek updated JDO-221:
---
Attachment: JDO-221.patch2
The second patch implements the comments above.
Test case AggregateResult misses DISTINCT queries and navigational
expressions
(the semantics of the method are such that a select
needs to be executed against the datastore anyway before the delete
occurs).
Another alternative is to disallow the Unique flag for
deletePersistentAll. But that's not what I would choose.
Craig
On Nov 25, 2005, at 6:07 AM, Michael Watzek wrote
[ http://issues.apache.org/jira/browse/JDO-226?page=all ]
Michael Watzek updated JDO-226:
---
Attachment: JDO-226.patch
The attached patch fixes this issue.
DistintCandidateInstances.testCollectionQueries typo
[ http://issues.apache.org/jira/browse/JDO-225?page=all ]
Michael Watzek updated JDO-225:
---
Attachment: JDO-225.patch
The attached file fixes this issue. However, the test case still fails throwing
the following exception:
[java] 2)
testConstructor
[ http://issues.apache.org/jira/browse/JDO-216?page=all ]
Michael Watzek resolved JDO-216:
Resolution: Fixed
The attached patch has been checked in including the comments above (Revisiov
345514).
Result handling in class QueryTest must
[ http://issues.apache.org/jira/browse/JDO-221?page=all ]
Michael Watzek updated JDO-221:
---
Attachment: JDO-221.patch
The attached patch fixes this issue.
Test case AggregateResult misses DISTINCT queries and navigational
expressions in aggrgate
[ http://issues.apache.org/jira/browse/JDO-222?page=all ]
Michael Watzek updated JDO-222:
---
Attachment: JDO-222.patch
The attached patch fixes this issue.
Test case query.sql.CandidateClass should renamed to
query.sql.NoCandidateClass
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
should add a
negative test case checking this.
Regards,
Michael
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin
[ http://issues.apache.org/jira/browse/JDO-223?page=all ]
Michael Watzek updated JDO-223:
---
Attachment: JDO-223.patch
The attached patch fixes this issue.
Additionally, the classes have been adapted to the new result handling
implemented as part of JDO
[ http://issues.apache.org/jira/browse/JDO-224?page=all ]
Michael Watzek updated JDO-224:
---
Attachment: JDO-224.patch
The attached patch fixes this issue.
Adapt ResultClassRequirements to new wording in spec concerning assertion
A14.6.12-1
:56 AM, Michael Watzek wrote:
Hi Andy,
I'm implementing test cases for deletion by query. Assertion A14.8-4
specifies (amongst others) that dirty instances are flushed to the
datastore before they are deleted.
The test case implementing this assertion adds a lifecycle listener
on the requested object.
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http
: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
Test case AggregateResult misses DISTINCT queries and navigational expressions
in aggregate queries for all aggregates, e.g
- SELECT COUNT(DISTINCT manager) FROM Employee
- SELECT COUNT
().
Key: JDO-223
URL: http://issues.apache.org/jira/browse/JDO-223
Project: JDO
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
SupportedMapMethods must be extended by queries calling isEmpty() and size():
- SELECT FROM
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
Method testNegative defines an invalid query which is valid wrt the new wording:
SELECT personid, lastname
INTO org.apache.jdo.tck.query.result.classes.LongString
FROM org.apache.jdo.tck.pc.company.FullTimeEmployee
[ http://issues.apache.org/jira/browse/JDO-219?page=all ]
Michael Watzek closed JDO-219:
--
Resolution: Duplicate
This issue is a duplicate of JDO-223.
JDO2 test cases miss queries testing methods size() and isEmpty() for both,
collection and maps
[ http://issues.apache.org/jira/browse/JDO-165?page=all ]
Michael Watzek updated JDO-165:
---
Attachment: JDO-165.patch2
The second patch implements the comments above.
Implement new JDO 2 query tests cases concerning SQL queries
, but is that important ?
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http
The type must match.
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
Test cases SupportedCollectionMethods and SupportedMapMethods must be extended
to include queries performing size() and isEmpty().
--
This message is automatically generated by JIRA.
-
If you think
Components: tck20
Reporter: Michael Watzek
Assigned to: Erik Bengtson
Query test case GetFetchPlan fails throwing the exception below.
The test case queries an instance of PCClass. PCClass has two persistent fields
and two corresponding transient fields which are set by jdoPostLoad
Type: Bug
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
The current result handling in class QueryTest cannot consider return types of
type java.lang.Object. Unique queries and queries using aggregates in the
select expression (single exression, no group
Type: Improvement
Components: tck20
Reporter: Michael Watzek
Assigned to: Michael Watzek
Priority: Minor
This issue depends on JDO-216.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
[ http://issues.apache.org/jira/browse/JDO-216?page=all ]
Michael Watzek updated JDO-216:
---
Attachment: JDO-216.patch
The attached patch implements the comments above.
Result handling in class QueryTest must be capable to consider return types
[ http://issues.apache.org/jira/browse/JDO-164?page=all ]
Michael Watzek updated JDO-164:
---
Attachment: JDO-164.patch2
The second patch implements the comments above.
Furthermore, the patch implements the comments in JDO-216 concerning the
expected
[ http://issues.apache.org/jira/browse/JDO-163?page=all ]
Michael Watzek updated JDO-163:
---
Attachment: JDO-163.patch3
The third patch fixes 2 issues reported by Andy on jdo-dev:
1. MetadataSearchOrder.testPackageJDOQuery - this complains about
[ http://issues.apache.org/jira/browse/JDO-164?page=all ]
Michael Watzek updated JDO-164:
---
Attachment: JDO-164.patch
The attached patch implements the assertions above.
Implement new JDO 2 query tests cases concerning result handling
--
Andy
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
---
.
What is the result of the following JDO query: SELECT COUNT(manager)
FROM Employee?
Is the result 4?
Regards,
Michael
--
---
Michael Watzek [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]Buelowstr
[ http://issues.apache.org/jira/browse/JDO-163?page=all ]
Michael Watzek resolved JDO-163:
Resolution: Fixed
The second patch has been checked in (Revision 331850).
Implement new JDO 2 query tests cases concerning query API Extensions
) SELECT manager FROM Employee WHERE lastname == 'emp2Last'
expected result: {null}
3) SELECT DISTINCT manager FROM Employee
expected result: {emp2, null}
Regards,
Michael
--
---
Michael Watzek [EMAIL PROTECTED
1 - 100 of 263 matches
Mail list logo
