[rules-users] Drools Flow client.getTasksAssignedAsPotentialOwner API returns duplicates - bug?

[gs76pl]

hi,

i've noticed that after creating two separate tasks (different names) for
the same user below query return 2x2=4 items from which two of them are
duplicates

minaClient.getTasksAssignedAsPotentialOwner("user","language",responseHandler)

List tasksOwned = responseHandler.getResults();

I've checked database and in fact there are only two rows in a Task table
but the above API calls multiple outer joins on different tables that cause
duplicates to be produced.

So, if this is an "intentional bug" and it is up to the calling method to
get rid of duplicates is there any other better/more efficient way of
working with tasks as it seems like the whole API is somehow flawed. I
suspect that with significant number of tasks the performance will be very
low



--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-client-getTasksAssignedAsPotentialOwner-API-returns-duplicates-bug-tp2666918p2666918.html
Sent from the Drools - User mailing list archive at Nabble.com.