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.
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 230
Foster City, CA 94404
(650) 242-3500 Main
(650) 242-3501 F
www.truviso.com
On Thu, Jul 22, 2010 at 9:38 AM, Matthew Wakeling <matthew@flymine.org> wrote:
> On Tue, 20 Jul 2010, Kris Jurka wrote:
>>
>> To me it seems like a protocol violation to receive CommandComplete(C) and
>> ReadyForQuery(Z) before we've issued CopyDone(c) and this should be fixed
>> server side.
>
> Is anyone following this up?
>
> Matthew
>
> --
> If you're thinking "Oh no, this lecturer thinks Turing Machines are a
> feasible
> method of computation, where's the door?", then you are in luck. There are
> some there, there, and by the side there. Oxygen masks will not drop from
> the
> ceiling... -- Computer Science Lecturer
>
