[#COR-736] Predicate doesn't work correctly if the parameter of match method is declared as Object.

db4o Core

Predicate doesn't work correctly if the parameter of match method is declared as Object.

Created: 24/Jul/07 01:08 PM Updated: 31/Jul/07 02:14 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

Denmark - v6.3

Time Tracking:

Original Estimate:

Not Specified

Remaining Estimate:

Time Spent:

5.5h

Peers:	Carl Rosenberger
Order:	3
Iteration:	1
Original IDS Estimate:	1
Resolution Date:	31/Jul/07 02:14 PM
First Response Date:	30/Jul/07 01:23 PM
Labels:
Participants:	Andrew Zhang and Patrick Roemer
Number of Attachments:	0
Number of Comments:	3

Description

« Hide

Please see com.db4o.db4ounit.common.assorted.ComparatorSortTestCase

public static class SmallerThanThreePredicate extends Predicate {
// FIXME: The test fails if we use Object as the parameter type.
public boolean match(Object candidate) {
return ((Item)candidate)._id<3;
}
}

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Andrew Zhang - 26/Jul/07 01:04 AM

Set the priority as critical since it blocks integrating the concurrency test suite into db4o test project.

[ Permlink | « Hide ]

Patrick Roemer - 30/Jul/07 01:23 PM

Doesn't look like a NQ issue, but rather a conceptual SODA problem: For an Object type extent, there is no QConClass created that a QConEvaluation could be attached to later.

[ Permlink | « Hide ]

Patrick Roemer - 30/Jul/07 03:16 PM

See UntypedEvaluationTestCase.