Protocol 2 vs 3

Protocol 2 vs 3

Postby dhoernig » Wed 04 Jun 2008 16:14

On other posts, I've seen the following advice:
Protocol 3.0 doesn't support multiple query execution.
To enable this, set Protocol=2.0 in your connection string.

I'm converting an app from using ODBC driver to PostgreSQLDirect .NET and in many cases use multiple select statements separated by ';'
Setting Protocol=2 in my connection string solves the problem, but am I losing other benefits or features by doing this?
Posts: 1
Joined: Wed 04 Jun 2008 16:03

Postby Alexey.mdr » Thu 05 Jun 2008 07:32

The main changes between protocols 2.0 and 3.0 are described here: ... anges.html
It's likely your application can gain some performance with protocol 3.0, but in this case you should change the code.
Posts: 729
Joined: Thu 13 Dec 2007 10:24

Return to dotConnect for PostgreSQL