Hello:
Uhmmm, if you don't mind... are you implementing something like a data
provider for Postgresql, or it is just an ad hoc program?
Well i start making a simple library for 3.0 protocol for curiosity only
:), the protocol have a great documentation, but after some some days
i decide to
Carlos Guzman Alvarez wrote:
Hello:
Uhmmm, if you don't mind... are you implementing something like a data
provider for Postgresql, or it is just an ad hoc program?
Well i start making a simple library for 3.0 protocol for curiosity only
:), the protocol have a great documentation, but after
Hello:
That's very good!
Do you know about Npgsql?
Yes i know about it, but i have no see it in deep ( i use Firebird as
RDBMS at this moment ), i decide to take a glance at the 3.0 protocol
using C# when i know about the plans for a native Windows version in 7.4
version :) , but i'm not sure
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.
Tom Lane wrote:
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
Carlos Guzman Alvarez wrote:
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
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 freezes
