Hello:
>You must send either Flush or Sync after the Parse to force the backend
>to emit its response to Parse. The assumption is that in many cases
>you'll be sending Parse as part of a batch of commands, and the backend
>should batch its responses to minimize the number of network packets
>sent
"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> writes:
> I'm implementing the 3.0 protocol version in Npgsql, a .Net Data
> provider for postgresql.
> I stopped in the first message: Parse :(
> I send the parse message but I don't receive the ParseComplete or the
> ErrorResponse. My code simply
Hi all,
I'm playing with this for one week with no luck... :(
I'm implementing the 3.0 protocol version in Npgsql, a .Net Data
provider for postgresql.
I could get it working using the simple query and so, I started to work
in the extended query.
I stopped in the first message: Parse :(
I
