Protocol 2 vs 3
Posted: Wed 04 Jun 2008 16:14
On other posts, I've seen the following advice:
Setting Protocol=2 in my connection string solves the problem, but am I losing other benefits or features by doing this?
I'm converting an app from using ODBC driver to PostgreSQLDirect .NET and in many cases use multiple select statements separated by ';'Protocol 3.0 doesn't support multiple query execution.
To enable this, set Protocol=2.0 in your connection string.
Setting Protocol=2 in my connection string solves the problem, but am I losing other benefits or features by doing this?