This problem did seem to be fixed for a while but it has reappeared about a
month ago, its taken
me a while to raise the issue.
I am using the latest nightly, 17th July 2009.
Updates to objects from Java cause duplicate indexes such that a GET on the
class returns multiple
entries of a specific object with the same id.
I have tried changing between transaction and transactionless commits of the
data and though this
can change behavior it does not fix the problem.
Original issue reported on code.google.com by pvolkaer...@gmail.com on 17 Jul 2009 at 8:20
Original issue reported on code.google.com by
pvolkaer...@gmail.com
on 17 Jul 2009 at 8:20