On Thu, 22 Jul 2010, Maciek Sakrejda wrote:
> Can you confirm Kris's theory? You should be able to do that by
> starting a binary copy with the CopyManager.copyIn(String), writing
> all your binary data to it, flushing, and then sleeping for a while
> before calling endCopy? If Kris is right, you should get the error
> after the flush before the endCopy. If that's the case, I can take a
> look at doing a patch this weekend. If I'm reading the protocol
> contract right, it ultimately should be fixed in the backend, though.
I can try and reproduce that. However, I will point out that the patch I
sent to the list which delays the reading of the Z does fix the problem.
Matthew
--
Ozzy: Life is full of disappointments.
Millie: No it isn't - I can always fit more in.
